We have an issue where changesets that have already been merged between 2 branches appear in the list when merging the opposite direction. I have blogged it but don't see a fix except way back in TFS 2010. We are on TFS 2013 Upgrade 5.
Example:
We have a trunk with a Dev branch.
Do some work in DEv, checkin changeset 1, merge to Trunk.
Now Trunk and Dev are in sync.
Now use the wizard to merge from Trunk down to dev. changeset 1 appears in the list when it shouldn't. The two branches are identical.
The scenario when you would need to do this are simply that changes were merged to Trunk from another branch or directly to trunk for a bug fix for example. Then you need to merge down from Trunk to Dev to get dev in sync with some changes that are necessary in Dev branch.
This used to work and it broke at some point in the 2008 or 2010 version. We are on 2013 and still an issue.
Can anybody tell me if this has been addressed?
Thanks.
tf merge /discard /baseless
? – stuartd