Bitbucket smart commits - do you need whitespace between each Jira issue ID?

Do I need whitespace between each Jira issue ID for smart commits to work?

For example, I know this will work:

"TKT-123 TKT-124 is a valid commit message #comment did some work"

But, I do not know if this will work:

"TKT-123: may not be a valid commit due to the : #comment will this work?"

I'm trying to come up with a standard commit message format that will work across multiple SCM tools and existing jira plugins for each SCM.

1 answer

0 votes

Hi Matt, the syntax of the smart commit requires a whitespace after the issue key as you can see at Smart commit messages:

<ignored text> ISSUE_KEY <ignored text> #comment <comment_string>

You could do, however:

"TKT-123 : commit message : #comment did some work"

(note the whitespace between the issue key and the colon )

Would that work for you?

Best regards :)


Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

689 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot