Jira Issue ID in Commit Message

[maheshrijal]

Would be good if I can include a Jira Issue Key / Link in the commit message prompt so that the commit message includes the Jira ID.

[Byron]

Thanks for the suggestion!

Even though there already is options to change the prompt for commit message generation…

…, the Jira ID would require knowing it and making it available in the prompt. Right now, we can only attach PR/MR numbers, but maybe one day we can have arbitrary key-value dicts stored with each branch, and made available for substitution in the generated message.

Do you think that would be what you want, or is there anything I am missing?
Thanks again.

[maheshrijal]

My internal workflow requires every commit start with a Jira issue key (Which I'm sure is common across orgs).

I was thinking a input field to provide the Jira Issue ID next to the generate message button or for the branch name, if it has a issue key, the commit message can read the branch name and add it in the generated message.

[Byron]

Thanks! This does sound like a per-stack or per-segment key-value store that can be used for templating would do the trick.

CC @krlvi as this should be much easier to do once ref-metadata is stored in the database. Nothing I see happening anytime soon, but it's good to keep in mind.

[maheshrijal]

I was experimenting with using cursor and gitbutler. This might be easier through the MCP if there was a way to pass custom instructions for generating a messaage & branch name.