• JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 months ago

      I must have read that blog post in the past because that’s exactly the style I use. Much of it is standard though.

      One MAJOR pet peeve of mine (and I admit it is just an opinion either way) is when people use lower case letters for the first line of the commit message. They typically argue that it is a sentence fragment so shouldn’t be capitalized. My counter is that the start of sentences, even fragmented ones, should be capitalized. Also, and more relevant, is that I view the first line of the commit more like the title of something than a sentence. So I use the Wikipedia style of capitalizing.

      • jaemo@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        https://gitmoji.dev/

        Quasi parallel reply to your other post, this would kind of echo the want for a capital letter at the start of the commit message. Icon indicates overall topic nature of commits.

        Lets say I am adding a database migration and my commit is the migration file and the schema. My commit message might be:

             🗃️ Add notes to Users table
        

        So anyone looking at the eventual pr will see the icon and know that this bunch of work will affect db without all that tedious “reading the code” part of the review, or for team members who didn’t participate in reviews.

        I was initially hesitant to adopt it but I have very reasonable, younger team mates for whom emojis are part of the standard vocabulary. I gradually came to appreciate and value the ability to convey more context in my commits this way. I’m still guilty of the occasionally overusing:

           ♻️ Fix the thing
        

        type messages when I’m lazy; doesn’t fix that bad habit, but I’m generally much happier reading mine or someone else’s PR commit summary with this extra bit of context added.