Utter Disregard for Git Commit History

https://zachholman.com/posts/git-commit-history/

by kiyanwang • 9 years ago

14 10 9 years ago

xkxx3• 9 years ago

If your commit messages are meaningless, why not make them empty? Like this: `git commit -m "" --allow-empty-message`.

It's like you didn't actually read the same article that I did. Nowhere does the author say that commit messages are meaningless. "foo", followed by "revert foo" carries a LOT of meaning. It means you tried something and it didn't work. If you leave that out of your history you risk not remembering that you tried something and that it didn't work. You don't have to look at the revert commit. For all other purposes, the two commits may as well not exist, but together they carry extremely useful meta information.

Disregarding the low level commit messages and using commit clusters for features allows you to easily track when and how this happens. Using single atomic feature commits does not.

xkxx3• 9 years ago

How is "Revert foo" different from "Revert 52e8ace0571ec9ac9b669bc5acfd0bcea537805d"?

Nowhere does the author say that commit messages are meaningless

He doesn't. I say it. His commit messages are meaningless. To understand what's going on, you need to read his diffs, not commit messages. In his workflow, only reverts and merges provide any context, and for them git creates meaningful commit messages automatically.

dwringer• 9 years ago

I shudder to think what kind of names he probably uses for local variables.

Pica_soO• 9 years ago

TL,DR: Pedantic People ranting about missing commit history. Slackers declaring it a art and "look into the diff". Not present- pragmatics training NN on the diffs, so that changelog messages get autogenerated.

BugsJustFindMe4• 9 years ago

This might be the least apt TLDR I've ever read. How did you come up with it?

anotheryou• 9 years ago

Personally I like to push as soon as it's not broken to have something to revert too. This also means e.g. function and design might be in different commits. Bundeling more together makes the commits easier to read, but leaves me without version history in between steps. Is there a trick to have both?

Utter Disregard for Git Commit History

Related Stories