13

My new favourite commit message:

"All changes as of 18th Sept"

How tremendously useful? There I was looking to know what changes were made to enable a feature / service, thought I could look for that in the commit message, but no you've given me a much more efficient way of finding out.

I simply need to download the contents of your memory, find out what date you made a change, and then dig through the massive commit to find the piece of info I need.

Forget experience using Git features, managing merges, following Git flow, or even any other SCM ... how can people be so tick when it comes to recording what they've done.

Heres a little cheat sheet for those struggling:

- Commit message
Describe what you actually ****ing did. Don't tell me the date or the time, thankfully Git records those. Don't tell me the day of the week, if I need to know I can figure that out, just tell me what ... you ... did.

- Feature branch names
Now this is a tricky one. You might be surprised to know that this isn't in fact suppose to be whatever random adjective or noun popped into your head ... I know, I too was shocked. The purpose of this is to let other people know what new feature is being worked on in this branch.

- Reusing feature branches
Now I know you started it to add some unit tests, and naming it "testing" is sort of ok. But its actually not ok to name it testing when you add 3 unit tests ... then rip out and replace 60% of the business logic. Perhaps it would have been wiser to create a new feature branch, given you are now working on a new feature.

Comments
  • 1
    My brain was not able to handle the complexity of info mentioned in his commit message, please next time only use "18th Sept"

    Good luck with that my friend, those are one of the worst things to deal with when working in team :\
  • 0
    @wolt it depends, if it is solely for testing, then that’s fine. If you test something and then merge it into develop, create another one named testing and merge it into develop and keep doing this over and over ... then no.

    Imagine 5 devs all working on the same project dealing with “testing”, “experimenting”, “new_idea”, “test”, “testing_2”. That’s insane to try and figure out what’s going on.
Add Comment