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

  • Kaldo@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    If a glorified autocomplete algorithm can write more informative and concise commit messages than you, the actual author behind the code, I think you need to sit down and think long and hard what that actually implies.

    • douglasg14b@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      11 months ago

      And what does it imply?

      That an AI might be better at writing documentation than the average dev, who is largely inept at writing good documentation?

      Understandably, as technical writing isn’t exactly a focus point or career growing thing for most devs. If it was, we would be writing much better code as well.

      I’ve seen my peers work, they could use something like this. I’d welcome it.

      • macniel@feddit.de
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        And what does it imply?

        it implies that the author of the code has no idea what they were doing.

  • deur@feddit.nl
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    11 months ago

    You realize you don’t need to list all your changes in the commit message, right? Anyone can blame or diff said changes.

    The commit message is meant to be used for the high level stuff, the intent, representing / connecting progress towards a larger work item, and other important context from outside the codebase. Insert other reasons that aren’t saying literally what was changed if you feel I have missed something.

    Also one should use their time better if they are spending so much time writing commit messages they feel the need to automate it. Commit messages are rarely read ever again (once merged, lets say), it is not okay to be spending a lot of time on them. That’s not an excuse to write bad commit messages, but you have to balance the time cost with expected utility.

    And an addendum to the above. Describing what you did without reasoning, context, or other information that isnt captured within the changes itself makes your commit messages entirely useless. It makes IDE-inserted in-line blame information useless as well. Thus you are now wasting all the time you spend on commit messages, even if you spend less because it’s automated.

  • packadal@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    I’m really curious to see examples of commit messages.

    And more details on how you achieved it, I’d like to give it a go myself, as some of my coworkers commit messages are less than stellar.

    Does it write in the conventional commit formalism ?