Since the branches are lightweight, switching between branches is quick and easy.
Git does not create multiple copies of your source when working with branches, it uses the history information stored in commits to recreate the files on a branch when you start working on it.
Your Git workflow should create and use branches for managing features and bugfixes.
The rest of the Git workflow, such as sharing code and reviewing code with pull requests all work through branches.
In this lab, you will learn how to establish a local Git repository, which can easily be synchronized with a centralized Git repository in Visual Studio Team Services.
The Git Hub pages for each plugin are good place to ask questions, find answers, and report issues.Ignore temp files, logs, and other files that might change but you do not want to stage in a commit.Git uses the parent reference information stored in each commit to manage a full history of your development.Share with your team the reason for locking the branch and make sure your team knows what to do to work with the branch after it is unlocked.Pull requests let your team give feedback on changes in feature branches before merging the code into the master branch.Use branch policies and pull requests instead of locking if you just want to ensure that changes in a branch are reviewed before they are merged.Locking does not prevent cloning of a repo or fetching updates made in the branch into your local repo.Manage the work in your Team Services Git repo from the Branches view on the web.Customize the view to track the branches you care most about so you can stay on top of changes made by your team.Isolating work in branches makes it very simple to change what you are working on by simply changing you current branch.Git keeps track of which branch you are working on and makes sure that when you checkout a branch your files match the most recent commit on the branch.