3 ms·
yeah, if you can do commits per function that would be fine. Most projects don't allow that, everyone squashes commits these days.
by linuxftw 4y ago
yeah, if you can do commits per function that would be fine. Most projects don't allow that, everyone squashes commits these days.
- kazinator 4y agoIf that's an argument so is this: most coders don't like commenting, nobody bothers, comments are haphazard and unmaintained. Just skip them. You don't seem to have understood my remarks; It's not "commit per function", but cover each function that was touched (or other entity: class, global variable, type, object member) in your commit comment. When someone does "git log" they should be able to search for the name of a function of interest and see all commits which touch it, explaining what was done to it and why. Banish squash commits; it's a poor CM practice. If you're not able to get your developers to commit to a good practice, then that's your main problem. You have to fix that before engaging "comment versus commit".