Show HN: Generate commit messages using GPT-3
1–10 of 73 posts
Re: Show HN: Generate commit messages using GPT-3
#2Some examples of commit messages it generates would be useful, especially compared to good commit messages like the ones usually found in the Linux kernel.
Re: Show HN: Generate commit messages using GPT-3
#3This creates precisely the kind of commit messages that I regularly scold junior developers for :)"
In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs.
But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
Re: Show HN: Generate commit messages using GPT-3
#4There is a similar tool: https://github.com/RomanHotsiy/commitgpt
Re: Show HN: Generate commit messages using GPT-3
#5This creates precisely the kind of commit messages that I regularly scold junior developers for :)" In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs. But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
Can you give some examples of good commit messages?
Re: Show HN: Generate commit messages using GPT-3
#6This creates precisely the kind of commit messages that I regularly scold junior developers for :)" In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs. But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
So this would be more appropriate as an "explain commit" tool, which would also evolve as gpt3 gets better
Re: Show HN: Generate commit messages using GPT-3
#7There is a similar tool: https://github.com/RomanHotsiy/commitgpt
That one appears to be non-functional
Re: Show HN: Generate commit messages using GPT-3
#8This creates precisely the kind of commit messages that I regularly scold junior developers for :)" In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs. But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
Can you give some examples of good commit messages?
Subjective and also depends on the culture where you work. I’ve worker at places where the majority of the “why” Is in a JIRA ticket, so the commit message better reference that ticket number. Not so at other places. See what I mean?
Re: Show HN: Generate commit messages using GPT-3
#9This creates precisely the kind of commit messages that I regularly scold junior developers for :)" In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs. But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
Why should the commit message explain why? I thought the point was to give a summary of the changes so that you don’t have to read the full diff.
Re: Show HN: Generate commit messages using GPT-3
#10This creates precisely the kind of commit messages that I regularly scold junior developers for :)" In my opinion, commit messages should clarify the intent of WHY you changed things. I can already see WHAT you changed from the diffs. But of course, any tool can only work with the what, they cannot know that these lines are related to a bug report filed in a technically unrelated system.
Can you give some examples of good commit messages?
Or, just squash your commits and focus on bigger things.