Over my decorated 10-year career in development, I have seen some of the worst commit messages. I don't blame the developer on this either, because...
For further actions, you may consider blocking this person and/or reporting abuse
git commit -vreally helps here. Since I started enforcing it on myself (through use of a shell function that intercepts all my attempts to rungit) my commit messages have got much better.git add --patch|-phas helped a lot in this also, both tools we all should be using, actuallyI have to walk a fine line, in this response, because...
First, if you don't remember what work you did, then you probably put too much into your commits. While I realize that nobody's perfect and things slip through the cracks, each commit should do a specific thing, and someone can ideally add a specific feature (and nothing else) by cherry-picking other otherwise moving a defined set of commits.
Then, changes (in a professional environment) should all be connected to a ticket, so that people can track the work happening without analyzing the repository. Commits should call out the relevant ticket numbers and probably echo the language used in the ticket. I'm never going to search a repository for "the time that Zemzem removed a text box." I want "the work done on ticket #4586, ideally seeing the individual tasks involved in finishing that ticket."
Finally, you're allowed to use a graphical interface, when you commit, and look at the changes that you're committing. Again, if you did a bunch of things at once, you should probably use such a tool, so that you can commit specific lines that go together, instead of full files.
Again, that doesn't take away from the technical achievement or the entertainment value. And (like anything with generative AI) if you use the results as a springboard to what you'll really write, that'll probably serve you better. But I definitely worry about trying to "outsource" communication with your closest colleagues...
Look like developers have the sam idea, I also did the same thing with you. But i named it ai-commit instead. Use conversation form to ajust the message
Please drop a link if its open source. Also to be clear this isn't my project, but a project open sourced by @nutlope
If you use VS Code the latest pre-release version of GitLens also provides the ability to use ChatGPT to generate commit messages (and probably soon to explain commits). There is even a setting so the user can control the commit message style as part of the prompt.
Nice one
It's nice, I tested it yesterday, but please note that too many commits (requests) in a short period of time will result in an error 400 - bad request. 👏🔝🎉
Good call out. There are some obvious areas of improvements and I think this project is set up well for some one to take what is already there and make something useful for a lot of people.
Adopted here ;-p
the too many requests are killing my vibe tho :<
It's very nice, but sometimes I'm too lazy to think about the commit message after the long hour code.
Very simple and inspiring implementation. I'll probably do a couple of experiments too =)
Hey there, are you using the latest version of AI Commits? Commits with imperative mood have been merged two weeks ago (see this PR) and merged but your screenshots do not reflect that and still use the past tense.
Screenshot is from the README.
Funny Project.
But i don't think that's a good idea to send all you code/commits to OpenAi.
Pretty sure your boss/client will not appreciate that.
Probably it's also against your NDA. Be cautious.
I really enjoyed reading your post about AI-generated git commit messages. As a developer myself, I can relate to the struggle of writing clear and informative commit messages. I think Nutlope/aicommits is a really interesting tool, and it's impressive to see how popular it has become in just two weeks.
I found it helpful that you took the time to explain how the AI part of the code works, and it's great to see how OpenAI is being used in practical applications. I agree with you that the createCompletion function is where the magic happens, and your comments on each line were very helpful in understanding what's going on.
I also appreciate that you shared your thoughts on the code and your experience with building CLIs. It's always great to hear from other developers and learn from their experiences.
Overall, I thought your post was well-written and informative. Thank you for sharing your insights and for encouraging others to contribute to open source projects. I look forward to reading more of your 30 days of OpenAI series, and I'll definitely check out Nutlope/aicommits!
I have waited for this!
Cool idea