It writes more informative commits than I could ever make so I’m just reading what it says and mostly copy/pasting completely most of the time, I write all of the changes I’ve made into an LLM with a large context window and it write a very detailed commit not just with a title but with bullet points describing each of the changes precisely

  • biddy@feddit.nl
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    1 year ago

    If it’s faster to get an AI to write your commit messages than to write them yourself, your commit messages are too long. They should be one sentence.

    • kablammy
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      1 year ago

      And if one sentence isn’t enough, the commit has too many changes

    • Alphare@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      1 year ago

      Strong disagree. Commit messages that are only one sentence long should be reserved for truly trivial things. Signed, someone who regularly comes back to 18+ year old commits and enjoys the valuable details that would have been lost.

      • learningduck@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        How about prefixing your commit with a ticket number?

        If a commit message has too much information, then the commit has too much changes

        • IAm_A_Complete_Idiot
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Not having to swap over to a ticketing system just to see the context of a change is really nice (Or to add context on why changes are done a certain way). One line that says what you changed, then any context such as why it was done that way, and important notes about that change works wonders. It’s pretty much the exact model the Linux kernel uses, and it makes looking at changes great for anyone down the line.