After seeing people use the @jetbrains UI to commit to git I understand where all those - sorry: shitty - commit messages come from…

🙈

An improvement would already be to have a “Subject” line and the text box.

And have the subject line follow the Beams Rule.

Sonthat the first line of the commit message finishes the sentence

“When this commit is applied it will…”

And please: No longer than 56(?) characters (Unicode). Keep it short. You got the textbox to explain *why* in full length.

    • Alerta! Alerta!@phpc.socialOP
      1·
      26 days ago

      @BatmanAoD Whatever tool people are using for their issues and/or PRs and/or VCS

      And it’s not about trusting the tool but trusting that the tool will always be available. Whether due to discontinuation of the tool itself or due to discontinued use of the tool and replacement by something else…

      • BatmanAoD@programming.dev
        1·
        26 days ago

        To be clear, you’re saying you trust git metadata to be preserved even when forge/issue-tracking/etc metadata is not?

        I suppose that’s probably the case more often than not. I think it’s still preferable to trust the forge you use than to spend any significant amount of time or effort trying to ensure that the team has strong enough commit-message discipline to compensate for the risk of losing data in an issue-tracker or forge.

        • Alerta! Alerta!@phpc.socialOP
          2·
          26 days ago

          @BatmanAoD so far I have seen more issue-trackes come and go than VCSs…

          So yes: Training developers in commit-discipline would for me not be wasted time and money.

          Cause from what I have seen so far the question is not *whether* the issue tracker changes but *when*.

          But OTOH: That’s just me (and some companies I worked at).

          YMMV