-2
A program to automatically generate commit messages locally without an LLM? (realbitcoin.cash)
submitted 2 weeks ago by to c/programming@programming.dev
42 comments fedilink hide all child comments
 

Ello Ello.

Can you recommend a program with which I can generate commit messages locally? I DO NOT want an LLM local or cloud API. What I want is a tiny or small language model. If I could easily swap or customize the model for each project, it would be better, too. So I could have smaller models for specific projects. I can do the training meself.

Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 2 weeks ago (4 children)

A commit message is not supposed to be a summary of the code. It is supposed to gives information that you cannot deduct from the diff. Like:

  • Is there an attached ticket ?
  • Does it produce side effects ?
  • Is it a quick and dirty fix just before the release ?
  • What are the consequence of the modification ?
  • Why you choose this approach instead of another ?
  • Why are you not able to add regression test ? etc ...

The first guy at Cursor that create the feature to generate commit message from diff is just a fucking moron that don't understand the role of a commit message.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 5 points 2 weeks ago

    Things I want to see in a commit message before an autogenerated dissection of the diff:

    • What you ate for lunch
    • Were you grumpy this morning
    • Was your cat an asshole and drop something from a kitchen table
    • Is green better colour than blue
    • Did you hurry when typing the commit message
    • afasfsafdas

    I can understand the diff, but I can't understand your reasoning and anything that gives me an inkling of your mind is better than rewording the diff.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 weeks ago (1 child)

    Bullshit. They should also be a summary of the diff. Why would I want to have to read the entire diff to know what the commit is even trying to do?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 weeks ago

    That's the role of the commit title, with tags if you follow https://www.conventionalcommits.org/ standard.

    99% of commit description will never be read. Only the title is usefull when you scroll to a git log.

    But, for the remaining 1%, it means you ended up doing a git blame, git bisect or any funky stuff like this to troubleshot a bug. And when you find the commit that introduced the regression, written by some dude that leaved the company 5 years ago and see a description like "Add the whatever method in whatever class that do the stuff explained by the doc written in the file"... Well, thanks bro. But why did you do this ?!!!

  • permalink
  • fedilink
  • source
  • parent