6 ms·
It is not a lot of work to write them. I use them for - Tracking work on specific jira tickets - Giving myself a simple/quick overview on what was done - Track
by battery423 6y ago
It is not a lot of work to write them.
I use them for
- Tracking work on specific jira tickets
- Giving myself a simple/quick overview on what was done
- Tracking down bugs by trying to understand if that code is doing what it should do (bug vs. on purpose)
- If i need to revert something, i revert a git commit. might just happend once a year but if required its fundamental
I'm also always slightly surprised about discussions from this topic: Its a nobrainer to just do it.
Its cumbersome if you have to explain to colleges, who are working with code for longer then a few month, why you should just write proper git commits.
It is like 'i'm allowed to write code which does a lot if things but pls exlpain to me again how i write a proper git commit message' :(