IT:AD:GitHub:HowTo:Change Issue State With Commit Commands [Notes]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

# IT:AD:GitHub:HowTo:Change Issue State With Commit Commands #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}


</callout>


## Summary ##

At this point in time (Q1/2019) GitHub's offering is not as rich as Bitbucket's offering. Bitbucket recognizes words in commit messages to close/put on hold/reopen/link any Bitbucket issue (see [[http://skysigal.com/it/ad/bitbucket/howto/close_issues_with_checkins]]).

If you are using Jira, one can also control Jira Tickets using [Smart Commit](https://confluence.atlassian.com/bitbucket/use-smart-commits-298979931.html) messages.


Whereas GitHub seems to only offer words to close issues.

One can 
* link to Azure WorkItems using the `AB#123` (`AB` is for *Azure Boards* as opposed to GitHub items) format.
* close Azure WorkItems using `Fixes AB#123` (but it doesn't recognize any other words).








## Resources ##

* https://confluence.atlassian.com/bitbucket/resolve-issues-automatically-when-users-push-code-221451126.html