4 ms·
I've seen that useful commit message make it incredibly easy to see where the code came from and is going. It also never gets 'out of sync' like code comments t
by hasmolo 6y ago
I've seen that useful commit message make it incredibly easy to see where the code came from and is going. It also never gets 'out of sync' like code comments tend to, as it's a comment on a static place in the code, not a dynamic one.
- pengaru 6y ago> It also never gets 'out of sync' like code comments tend to, as it's a comment on a static place in the code, not a dynamic one. That's simply not true, not in a git world where rebasing to rewrite history is standard practice.
- urxvtcd 6y agoThe branches you rebase most of the time are your own topic branches, where you know what's going on. And they should be relatively short-lived.
- ulrikrasmussen 6y agoIn that case rebasing rather than merging would be the wrong choice, since you're actively obfuscating the history.
- Groxx 6y agoI don't see how this can possibly be relevant to how relevant a commit message is.