Cherry-picking for fun and profit
I used to be under the impression that I had to be extra formal and maintain a proper etiquette when writing git commit messages. After all, my work flow mostly consists of hacking on a branch, merging all the commits into master and the pushing upstream.
Whenever I felt like committing I used to think: "Well, this doesn't really mark a milestone in anything. Why would it make sense to have it on the main branch as a commit for the future generations to see?"
Turns out I was doing it all wrong because I had yet to meet
and didn't know you could "mash" commits together.
So suppose you start working on
* 6390118 (master) third commit kirbuchi, 2 minutes ago * 40a6dfc second commit kirbuchi, 3 minutes ago * 03b732e (HEAD, my_working_branch) first commit kirbuchi, 4 minutes ago
After a harsh battle with the new feature you're trying to implement, your new branch won't probably look so pretty. As a matter of fact, depending on your temper or what kind of day you're having, it may look something like this, if you don't hold back:
* e2124ed (HEAD, my_working_branch) work you piece of shit kirbuchi, 30 seconds ago * 371d5c0 oh god, why? kirbuchi, 79 seconds ago * 60d176c now it's hopefully ok kirbuchi, 1 minute ago * c8c3ce3 another change kirbuchi, 2 minutes ago * f7fd2b5 some tweak kirbuchi, 3 minutes ago | * 6390118 (master) third commit kirbuchi, 5 minutes ago | * 40a6dfc second commit kirbuchi, 6 minutes ago |/ * 03b732e first commit kirbuchi, 7 minutes ago
Of course you don't want your coworkers to stop thinking you're a nice guy so you may do the following.
git checkout master git cherry-pick -n ..my_working_branch
-n options tells git not to merge all the commits on top of you current
branch but instead to have their changes applied on top of you working tree.
Then you can commit with a more appropriate message.
git commit -m "Implemented new feature X"
And have everything look nice and presentable:
* 83449fa (HEAD, master) Implemented new feature X kirbuchi, 10 minutes ago * 6390118 third commit kirbuchi, 13 minutes ago * 40a6dfc second commit kirbuchi, 14 minutes ago * 03b732e first commit kirbuchi, 15 minutes ago
Having this in mind, I now see a commit sort of like a save on one of those old console emulators where you could save and load your progress immediately if you die or screw up.