top | item 45460045

(no title)

WildGreenLeave | 5 months ago

It is missing the (to me) most important part. The reason why these changes are made.

discuss

order

jjcob|5 months ago

I hate it when I look at some code, wondering why I added a refresh call at that point, I do a git blame to find the commit message, and it says "add refresh call".

rkomorn|5 months ago

But... I keep being told that commit messages are useless because the code is the documentation, so code diffs are self-explanatory...

_joel|4 months ago

Set a PR template up, that demands those sections are filled in. Could probably do that down to the commit level with pre-commit but realistically you'd want that level of detail in the in the PR. Also add issue id to the commits too, that way you can pull them up easily and get more context.

stpedgwdgfhgdd|5 months ago

True, you need to instruct the AI agents to include this.

In our case the agent has access to Jira and has wider knowledge. For commit messages i don’t bother that much anymore (i realise typing this), but for the MRs I do. Here i have to instruct it to remove implementation details.

DaiPlusPlus|5 months ago

> you need to instruct the AI agents to include this.

The agent can't do that if you told Claudepilotemini directly to make some change without telling it why you were prompting it to make such a change. LLMs might appear magic, but they aren't (yet) psychic.

darrenf|5 months ago

Isn't "Fix dynamic channel list" the reason?