Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Visual Studio 2019 | Visual Studio 2022
The first commit in a new Git repo is the start of the main branch. As you work in the main branch, you make commits to record your work in that branch. Branching in Git occurs when you create a new line of development that diverges from a prior branch. You might choose to create a new branch to develop and test a new feature before adding it to your main branch. The recommended Git workflow is to use a new branch for every feature or bugfix. When you switch between branches, Git almost instantly switches the version of your repo files to match the branch you selected. Your commits are always saved to the current branch, and are isolated from commits in other branches.
- View code in private projects: At least Basic access. - Clone or contribute to code in private projects: Member of the Contributors security group or corresponding permissions in the project. - Set branch or repository permissions: Manage permissions permissions for the branch or repository. - Change default branch: Edit policies permissions for the repository. - Import a repository: Member of the Project Administrators security group or Git project-level Create repository permission set to Allow. For more information, see Set Git repository permissions.
- View code: At least Basic access. - Clone or contribute to code: Member of the Contributors security group or corresponding permissions in the project.
Branch names can't contain ASCII control characters, such as spaces, tildes, and colons. It's common practice to use lowercase characters and to separate words with a hyphen. Forward slashes can be used to group branches. Branch name length shouldn't exceed 250 ASCII characters. To avoid ambiguity between branch names and commit hashes, don't use branch names that consist of 40 hexadecimal characters. For more information on branch naming, see git-check-ref-format and Git cross-platform compatibility.
You can create branches in Azure Repos Git repos, GitHub repos, or other hosted Git repos.
Azure Repos
From your web browser, open the team project for your Azure DevOps organization, and then choose Repos > Branches to open the Branches view.
In the Branches view, choose New branch to launch the Create a branch dialog.
In the Create a branch dialog, enter a unique new branch name, select a base branch for your new branch, optionally link work items, and then choose Create.
Your new branch shows up in the branch list.
GitHub
From your web browser, navigate to the main page of your GitHub repo, select a base branch to launch the Switch branches/tags dialog, enter a unique new branch name, and then choose Create branch.
The main page of your repo now shows the files in your new branch.
Tip
After you've created a remote branch, you can fetch it into your local Git repo. At the command prompt, run: git fetch git switch <remote branch name>
Visual Studio 2022 provides a Git version control experience by using the Git menu, Git Changes, and through context menus in Solution Explorer. Visual Studio 2019 version 16.8 also offers the Team Explorer Git user interface. For more information, see the Visual Studio 2019 - Team Explorer tab.
From the Git menu on the menu bar, choose New Branch to open the Create a new branch window.
In the Create a new branch window, enter a descriptive branch name to let others know what work the branch contains. By default, Visual Studio creates your new branch from the current branch. The Checkout branch checkbox automatically switches you to the newly created branch. Select Create.
Visual Studio 2019 provides a Git version control experience by using the Git menu, Git Changes, and through context menus in Solution Explorer.
From the Git menu on the menu bar, choose New Branch to open the Create a new branch window.
In the Create a new branch window, enter a descriptive branch name to let others know what work the branch contains. By default, Visual Studio creates your new branch from the current branch. The Checkout branch checkbox automatically switches you to the newly created branch. Select Create.
Visual Studio 2019 version 16.8 and later versions provides a Git version control experience while maintaining the Team Explorer Git user interface. To use Team Explorer, uncheck Tools > Options > Preview Features > New Git user experience from the menu bar. You can use Git features from either interface interchangeably.
In Team Explorer, select the Home button and choose Branches.
Right-click the default branch, often named main, and then choose New Local Branch From
Enter a descriptive branch name to let others know what work the branch contains. Select Create Branch.
To create a new branch, use the git branch command. This command doesn't switch your current branch to the new branch.
git branch <new branch name>
To switch to a branch, use the git checkout command.
git checkout <existing branch name>
To create and switch to a branch in one command, use the git checkout command with the -b flag.
git checkout -b <new branch name>
Tip
You can also use git switch <existing branch name> to switch to a new branch. Or, to create and switch to a new branch in one command, use git switch -c <new branch name>.
Do you want to work with different branches in Git to separate your development code from the code in production? In this module we'll discuss how you can work with branches in Git and merge your modifications.