Four rules of thumb for committing code

  • The commit message should explain Why, not what
  • Atomic commit. As small as possible
  • Don’t commit commented out code. Just remove it.
  • Before it goes into master/trunk, always have at least two sets of eyes on it. You only have one set even if you have glasses.

2 replies on “Four rules of thumb for committing code”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.