![]() I think Nutlope/aicommits is a really interesting tool, and it's impressive to see how popular it has become in just two weeks. As a developer myself, I can relate to the struggle of writing clear and informative commit messages. I really enjoyed reading your post about AI-generated git commit messages. But I definitely worry about trying to "outsource" communication with your closest colleagues. 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. 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.Īgain, that doesn't take away from the technical achievement or the entertainment value. 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."įinally, you're allowed to use a graphical interface, when you commit, and look at the changes that you're committing. Commits should call out the relevant ticket numbers and probably echo the language used in the ticket. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |