Is it possible to default seed the commit comment (but not for merges) with the branch name?

[David Mills]

Hi, we are finding that developers are often incorrectly typing in the JIRA ticket number in the commit comment. We do all our work on JIRA branches and so if we could get Sourcetree to seed the commit comment with the branch name this would remove this issue.
The result of the current situation is that quite a number of JIRA issues show no commits, builds, deploys, etc. And reports produced deom Bamboo, Stash and JIRA are missing these tickets.

[Intel CHD Jira Admin]

I would like this also! See SRCTREEWIN-3261 and https://answers.atlassian.com/questions/16388104

[David Mills]

One solution is to add the file commit-msg to every clone's .git/hooks folder with contents similar to: {quote} #!/bin/sh # # An example hook script to check the commit log message. # Called by "git commit" with one argument, the name of the file # that has the commit message. The hook should exit with non-zero # status after issuing an appropriate message if it wants to stop the # commit. The hook is allowed to edit the commit message file. # # To enable this hook, rename this file to "commit-msg". BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD) echo "Committing to branch: $BRANCH_NAME" > $1.new echo "User commit comments:" >> $1.new cat $1 >> $1.new mv $1.new $1 {quote}

[David Mills]

But this is a pain as you need to remember to add each and every time you create a clone.

[David Mills]

We found, installed, configured and use the "Yet Another Commit Checker" add-on which works well for this issue.

We ensure that:

• the committer matches
• The JIRA Ticket is valid
• That the assignee is the user and that the status is "in progress"