this post was submitted on 03 Nov 2023
30 points (67.4% liked)

Programming

17024 readers
256 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] PoisonedPrisonPanda@discuss.tchncs.de 2 points 10 months ago (1 children)

Im more in favour in writting "my" commit message myself and let LLMs refotmulate and make concise.

[–] TootSweet@lemmy.world 1 points 10 months ago* (last edited 10 months ago) (1 children)

Precision > concision && accuracy > concision. Just use your own wording as the commit message. I'd rather see an account of a code change from the viewpoint of the change's author than a shorter reformulation, even if that reformulation did come from a human who knew the problem space and wasn't prone to making shit up on the fly.

[–] balder1993@programming.dev 1 points 10 months ago* (last edited 10 months ago)

The problem is people are lazy and most places I’ve been, peoeple make bad commit messages and often very non informative.