3 ms·

Put the comments in git commit messages! Ha, that’s a good laugh. There are so many shortcomings to this, I don’t even know where to begin.

• kazinator 4y ago
  Nick checks out?
  • Izkata 4y ago
    The obsession people seem to have with squashing commits in git (particularly on merge) means they're right, you can't really rely on commit messages still containing relevant information.
    • kazinator 4y ago
      Squashing commits in this way would not have been allowed anywhere I've worked in at least 20 years. This is a strawman argument. Let's assume best CM practices (no vandalism of change sets when moving changes among branches), best practices for commit messages and best practices for commenting. Commit messages win. Code comments should be like road signs. E.g. how high can your truck be to pass under the upcoming bridge. Not blueprints for the bridge, or paragraphs about why it was built there, what communities it serves. (That information must exist and be available, just not on the bridge.)