If your git squash contains all the commit messages, it’s a pain to figure out w... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		josephg on July 7, 2023 \| parent \| context \| favorite \| on: Open source code with profanity in comments is sta... If your git squash contains all the commit messages, it’s a pain to figure out which commit message refers to which line of code. A comment goes right there. No tools needed. Mutable. Readable. Contextually in place. And you can even add comments while coding without waiting for the commit. Is typing // really so much effort?

cerved on July 7, 2023 [–]

No it's not and neither is writing a proper commit message. That's why you do both, but most of it goes in the commit. Like in the Git project

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact