Traceability after merge - What was the source branch?

Hot Topic

Independent Source Control Trees
Assigned To Field - Full name insted of User Name
TF Power Toy utility for RC?
How can a Team architect make diagrams visible for developers
TFS MSSCCI Provider Final fails to install
DoNotMarkEnumsWithFlags
Is it possible to queue Team Builds?
Reverse Engineering C# projects
Customizing build steps in Team Build
TF hanging

VS Team System

Combine Team Explorer and SCE
Synchronizing Predecessor Info between VSTS and Project
Data Tier Problem
WebRecorder / Fiddlertool and its limitations - Best way for recording IE's 'non-navigational' events
Problems with MSTest.exe
Estimation & Scheduling with VSTS
Create Tests doesn't work...
Error loading task list into Project
SQL Error on Get Latest
Team foundation server Dual server set up - Rebinding the data tier to the app tier

Traceability after merge - What was the source branch?

Hi,

I would like to know how can I know after a merge what was the source of the merge.


Suppose I merge from one branch to another. After the merge action I only have a new changeset at the target branch, from that changeset I can not know what was the source of the merge. 

Thanks

Yaarit

Answer this question

Traceability after merge - What was the source branch?

  • Richard Chauvet

    The best answer I have for v1 is to write helpful changeset notes when you check in a merge.  Comments & checkin notes are not displayed by 'tf merges' but they are returned by the QueryMerges web service call.  You can also view them in the IDE of course by doubleclicking on a changeset in the History toolwindow.

    The info you (and we!) want is already stored in the database's merge history rows, so I'm confident we'll do better in v2.

  • kablou

    Hi Richard,

    Yes I looked at the merges command, However you only receive the changeset's number, and if you want to know where it actually came from you need to search where that changeset came from.


    10x 

    Yaarit      < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

  • LazyCat

    You're right.  I thought there was a /format:detailed switch that would do what you're looking for, but I think it was cut.  In fact, even if you view the changeset, there's no information on where the merge came from (unless you typed something helpful in the Comments field).  I need to check whether there's a workaround.

  • robbyd

    Hi Yaarit,

    Have a look at the Merges command: http://msdn2.microsoft.com/en-us/library/656cs2x5.aspx
  • Traceability after merge - What was the source branch?
Answer this question