Tfs generate list of changesets and updating work items

But a lot of developers like to use other Git tooling, such as Git Extensions, Source Tree or the command line.And then we have the teams that work on other platforms, perhaps developing i OS apps but store their source code in a Git repo in TFS.You can view a changeset to see what the exact file changes were, discover the owner's comments, find linked work items, and see if any policy warnings were triggered.

Not in itself, but in the traceability that this gives us.For example, let’s say you have a DEV-MAIN-LIVE branching hierarchy.Presumably, you’ll work on DEV and do a bunch of checkins.Without this, we would have to rely on check-in comments from the developers to understand the reason for a particular change, not always easy when you look at changes that were done a few years back!When using Git repos in TFS, and you use the Git integration in Visual Studio you have the same functionality that lets you associate a work item to a commit, either by using a work item query or by specifying a work item ID.In the default template, both the label arguments are blank so the activity will work out which to use, but we can provide our own values to override that behaviour.


Leave a Reply