Because what we need is more of the what was done, with no regard to the why. Why provide any context as to why the change was made when you can fill it with an AI description of what one could accurately tell by looking at the code? I kinda can't believe this isn't a joke. Just squash it to the emoji that best captures the sentiment! Why use the tool to enhance you and your peers lives, when you can use AI to make it pointless!
Gptcommit: Never write a commit message again (with the help of GPT-3)
11–20 of 106 posts
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#12I can kind of understand getting help writing the description of a large PR. But a commit message? Whose commits are so long so often that they need the help of an AI assistant to come up with the contents?
Heh… there are really two types of coders. Those who things commits should have a single, obvious, minimal purpose, and who will split off unrelated changes into separate commits…
… and those who tag you as a reviewer on +8,298, -1,943 commits/PRs with the commit message "JIRA-PROJ-84138".
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#13I find commit messages have more value when they don't just repeat what you can see by looking at a diff but when they explain the reasons behind.
I was hoping GPT-3 was going to give the reasons
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#14This is interesting but I’d hate to work on a project where this was used. Commits should tell me why a change happened not just what code changed.
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#15I can kind of understand getting help writing the description of a large PR. But a commit message? Whose commits are so long so often that they need the help of an AI assistant to come up with the contents?
Heh… there are really two types of coders. Those who things commits should have a single, obvious, minimal purpose, and who will split off unrelated changes into separate commits… … and those who tag you as a reviewer on +8,298, -1,943 commits/PRs with the commit message "JIRA-PROJ-84138".
> … and those who tag you as a reviewer on +8,298, -1,943 commits/PRs with the commit message "JIRA-PROJ-84138".
At my workplaces, we've told people who do this to break up their larger commit into smaller ones before reviewing. If they haven't done that initially, well, their life is going to get harder for a few days.
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#16Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#17I find commit messages have more value when they don't just repeat what you can see by looking at a diff but when they explain the reasons behind.
The point of a summarization model is if you have a thousand line change, it helps to have a one sentence explanation of what it is. The demo videos the author used here really don't do a good job communicating that, because the summary GPT-3 wrote for his one line commit was longer than the commit itself.
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#18I don't really ever want to read answers from GPT to questions that I didn't knowingly myself ask GPT. If GPT can write a commit message from you, don't write it at all and let me ask it that if that's what I want. It may be a positive to you to spend a few seconds less on commit messages but it's a net negative for the world for it to become polluted with vast amounts of flatly incorrect text with no knowledge as to its provenance. I'd rather have no commit message than one that I can't trust whether it's written by the same human that wrote the code or not.
Put another way, you asking GPT for stuff that it learned from Stack Overflow: good. Using it to post to Stack Overflow: bad.
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#19Earlier quoted context omitted.
I was hoping GPT-3 was going to give the reasons
yeah and find the bugs.
I've had ChatGPT find some pretty esoteric bugs in ways that shocked me.
Like semi-jokingly asking it to "improve" some code thinking it'd come up with some non obvious control flow... then instead having it immediately point out a subtle bug along the lines of "the code sets flag A instead of setting flag B on " flag B wasn't even unused, so it's not like a simple unused variable heuristic would have caught that.
Re: Gptcommit: Never write a commit message again (with the help of GPT-3)
#20I don't really ever want to read answers from GPT to questions that I didn't knowingly myself ask GPT. If GPT can write a commit message from you, don't write it at all and let me ask it that if that's what I want. It may be a positive to you to spend a few seconds less on commit messages but it's a net negative for the world for it to become polluted with vast amounts of flatly incorrect text with no knowledge as to…
Except for startups when commit messages are more like "asdf", "aoeu", "quick fix", or "demo" because some investor barged in and demanded a demo before they would wire funds.
If ChatGPT could change that to something like "disable current limits" or "disable safety checks" or whatever that might be marginally better.