title: Associating git commits with Team Foundation work items
body: <p><strong>Context</strong></p>
  
  <p>A GitHub Enterprise installation used for development. Every developer has his own public repo, and the organization has the authorative repo. Pull requests are used for code reviews, and we loosely follow nvie's <a href="http://nvie.com/posts/a-successful-git-branching-model/">git flow</a> branching model. </p>
  
  <p>A TFS installation used for issue tracking and deployment (the release branch). We mirror the release branch into a TFS repo.</p>
  
  <p><strong>Work Items</strong></p>
  
  <p>Now the hard part is: How do we associate git commits (that may originally be done on the public branches of the developers) with TF work items? </p>
  
  <p><strong>What I did</strong></p>
  
  <p>I've looked at the following projects for help: </p>
  
  <ul>
  <li><a href="https://github.com/git-tfs/git-tfs">Git-TFS</a></li>
  <li><a href="https://github.com/nodirt/git-tf">Git-TF (nodirt)</a></li>
  <li><a href="http://gittf.codeplex.com/">Git-TF (microsoft)</a></li>
  </ul>
  
  <p>I've read references to associating commits with work item in both Git-TF projects, but I am unsure what tool to use, and how to go about it exactly.</p>
  
  <p>I would be fine if I had to run a script on the release branch commits to extract work item references from the commit message and associate them with changesets sent to TFS. However, a solution that allows the association in metadata (instead of commit messages) would be preferred. </p>
  
  <p><strong>What are my options to associate work items in TFS with git commits?</strong></p>