4 ms·

There isn't a lot that peeves me more than working with developers with poor git commit habits. As someone who takes every commit they make seriously, it can re

There isn't a lot that peeves me more than working with developers with poor git commit habits. As someone who takes every commit they make seriously, it can really demotivate/depress me when I look at my team's git log and see a series of poorly thought out commits and messages. It's always enjoyable to look at a piece of code, wonder why it is the way it is and to find that answer in a well written commit message by the author of the change. If a tool like his can at least help developers keep the diff portion of their commits usable, then I hope more people consider using it. It'd be interesting if it could learn from a project's history and have a developer confirm that they really want to commit files that it has determined to be unrelated, together.

nathancahill 10y ago
Same. Last project I worked on, most people used git add ., git commit, without ever looking at what was staged. The peeves were real. I'd love a tool that didn't let you commit unrelated files.
- jbverschoor 10y ago
  And that's how you find those lovely credentials on github.
e40 10y ago
What fixed this for us is Gerrit. http://code.google.com/p/gerrit/ http://code.google.com/p/gerrit/ It's been fantastic. People fear change, but after a short while, everyone was digging the benefits of commenting on other people's code and other people helping them make their code better.