August 2019
Beginner
608 pages
16h 7m
English
Compared to branches in Git, which are repository scoped, TFVC branches are path scoped and not as lightweight. Generally speaking, team members create additional workspaces for each branch they are working on. Changes are branch-independent, so to avoid chaos at integration time, you need to forward-integrate as many times as possible. The standard merge with TFVC uses a two-way merge (baseless).
Set your bar for creating branches high and only branch when you have a need for code or release isolation. It's more resource-intensive to use branches in TFVC. As the number of your feature branches increases, so do your storage requirements and branch hierarchy visualization fuzziness. In the following screenshot, ...
Read now
Unlock full access