Resolve issues automatically when users push code in Bitbucket and GitHub
Posted by jpluimers on 2015/05/14
I tend to forget some of the keywords you can put into BitBucket commit messages to relate them to certain issues/bugs/tickets
Below is the table I “borrowed” from the Bitbucket documentation.
Note at the start of the documented the image with the “cset” marking: that’s how an issue refers back to a change set.
These bitbucket cset links seem to be undocumented, but this is what happens:
A “cset” link will be automagically inserted in the issue when you mark the comment of the changeset with any of the below tags/actions.
The hex digits after the “cset” is the hash of the changeset.
The cool thing: these keywords for GitHub are largely the same.
Github keywords:
- close
- closes
- closed
- fix
- fixes
- fixed
- resolve
- resolves
- resolved
Bitbucket table:
resolve an issue
- close
- closes
- closed
- closing
- fix
- fixed
- fixes
- fixing
- resolve
- resolves
- resolved
- resolving
close #845
fix bug #89
fixes issue 746resolving #3117reopen an issue
- reopen
- reopens
- reopening
reopening #78mark an issue on hold
- hold
- holds
- holding
mark an issue wontfix
- wontfix
mark an issue invalid
- invalidate
- invalidates
- invalidated
- invalidating
link to a changeset for the issue
- addresses
- re
- references
- ref
- refs
- see
see #34 and #456
–jeroen
via:
- Resolve issues automatically when users push code – Bitbucket – Atlassian Documentation.
- Closing issues via commit messages · GitHub Help.
The Wiert Corner - irregular stream of stuff 
Leave a Reply