Open rambaliga opened 4 years ago
You would re-run this script using SOURCE and TARGET workspaces against those different stream histories and changing the local Git branch between each run (starting with a new local Git branch with no history.)
Unlike RTC, and most of IBM's tools, Git doesn't care about directory or file identity, so it will correctly merge content that exists in the same paths across multiple branches, you don't need to deal with moronic file identity issues like evil twins in RTC.
Currently we are trying to migrate multiple streams with one single component across all these streams set at different baselines.
Can anyone suggest how can this be achieved using this tool?