‹ BackHN Continuity

Thread

Commit description as a thinking tool

130 points · 78 comments · yedhukrishnan

  1. arialdomartini · · focus · HN ↗
    On top of this, it pays off to write the commit messages before the code

    <a href="https:&#x2F;&#x2F;arialdomartini.github.io&#x2F;pre-emptive-commit-comments" rel="nofollow">https:&#x2F;&#x2F;arialdomartini.github.io&#x2F;pre-emptive-commit-comments

    1. drdaeman · · focus · HN ↗
      Jujutsu is perfect for that - you create new changeset upfront, providing message at the same time (which can be later amended as needed). Feels so much more logical to declare the topic first, rather than come back to some accidentally uncommitted changes and wonder what was doing there.
      1. 1718627440 · · focus · HN ↗
        You can start to write the commit message first in Git too. (And I do that.)
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.