4 ms·
Tools such as this should not be used. The generated commit messages are all noise, no signal. The LLM can not possibly describe why a change was made, and it c
by xorcist 2y ago
Tools such as this should not be used. The generated commit messages are all noise, no signal. The LLM can not possibly describe why a change was made, and it can never describe why a corresponding more obvious change was not made.
Should you somehow find yourself in a situation where the above does not hold, and you really want the LLM description, it is still bad design to run the LLM on commit. LLMs will only get better over time. In that case you should not use commit messages but run the LLM on "git log" instead.
Just as it uses heuristics to show moved files it is also the more suitable place to summarize the diff, if that is all you place in the commit message field anyway. At that stage it has potential knowledge of the future as well, with that added context the summary might actually be useful ("this functionality is later replaced with ..").
- Mountain_Skies 2y agoIt reminds me of the trend of companies now requiring cover letters as they can use an LLM to summarize them. Now many job candidates are using LLMs to generate their cover letters. So LLMs are now trying to convince other LLMs of a human's fitness for a job. Between the job seeker's prompt and what HR sees from the LLM's summary, lots of noise is passed around and what little signal is there is likely lost.