11

Commit as you go. Work on one thing at a time. Be detailed in your commit messages.

Finding and reverting that one small change that breaks everything is so much harder to do when you change lots of files and the commit message is "update".

Comments
  • 2
    Use the blame and file history feature. You can see who touched what, and when for each file.
    Reverting the changes though.... not as simple.
  • 0
    Break down the changes and do clarified commits - that's my way around it.
Add Comment