3 ms·
Our standard of practice is to document the “why” in Jira. Then reference that card in the commit message. This gives product owners the ability to embellish a
by SamuelAdams 7mo ago
Our standard of practice is to document the “why” in Jira. Then reference that card in the commit message.
This gives product owners the ability to embellish as they wish and reduces the need of the dev to repeat themselves.
- vidimitrov 7mo agoThat’s cool. But how does it work in agentic environment? Do you get any benefit from it? Or it’s intended only for humans to read?
- pamcake 7mo ago> how does it work in agentic environment? Giving agent scoped access to ticket system. Whis is this obvious answer not the obvious solution?
- jiehong 7mo agoAnd someday jira is dumped for a different system and tickets slowly become unavailable. But, perhaps the IDE could retrieve the details of the jira card, and help pre-generate the commit message from it. If only tickets would be part of the repository itself from the beginning, that would be much simpler IMO.