In a collaborative environment, it is common for several developers to share and work on the same source code. While some developers will be fixing bugs, others will be implementing new features, etc. With so much going on, there needs to be a system for managing different versions of the same code base.
Project branching allows each developer to checkout code from the existing git branch and isolates their work from others.
What is a Project branch?
A Project branch is essentially an independent line of development checked out from the git branch. You can take advantage of Project branching when working on new features or bug fixes because it isolates your work from other team members.
Creating a new Project branch does not change the repository. It simply checkout the code from the existing git branch.
- Active Team Subscription
- External VCS configuration, see Code Repository
How does it work?
Create a Project branch
- Select Create Project Branch option.
- Next, select the existing git branch. Your project branch will be backed by this git branch.
- If you go to configured VCS; for example, GitHub. You can see there are two branches to pick from in the branch drop-down.
All the changes in the project branch will be backed by the selected git branch.
For more information on configuring VCS, see Code Repository.
- Project branch gets created pointing to the selected git-branch. Now, one can work independently on the feature-1 project branch without affecting the master branch code. Later, the feature-1 git-branch can be manually merged from the VCS system into the master branch.
Switching Project Branches
Switch to different project branches by clicking the branch, and you can see the changes you made on that branch.
Changes in master project branch.
- Changes in feature-1 project branch.