CODEWITHSUNDEEP
user-interfacetfsmergebranch
Lasse V. Karlsen
Lasse V. Karlsen

Reputation: 391396

Hide changesets from merge dialogs in TFS 2008 (2010)?

When merging from one branch to another, we can see which changesets are present in one branch, and yet not merged over to the other.

Some of these changesets aren't supposed to be merged. Is it possible to hide these?

Or do we just have to edit the changeset comments to include a prefix, like "NOMERGE:", to visually filter them out?

The reason I ask is that from time to time a developer forgets to merge changes that were supposed to be merged, and it's a bit hard to find these in a forest of other changesets.

Upvotes: 1

Views: 1278

Answers (2)

Ewald Hofman
Ewald Hofman

Reputation: 12668

You can use the TF MERGE /DISCARD option

http://blogs.msdn.com/b/mohamedg/archive/2009/03/09/how-to-use-tf-merge-discard.aspx

Upvotes: 2

softveda
softveda

Reputation: 11066

This is a strange question, why are some changesets not supposed to be merged and how do you determine those. If you are doing selective merges to me it looks like the branches are not created properly. I don't think you can hide changesets using Visual Studio. Using TF.exe command line application however you can find out what changesets are candidates in a merge and then merge individual changesets selectively see http://msdn.microsoft.com/en-us/library/bd6dxhfy.aspx

Upvotes: 2

Related Questions