Sourcetree checkout a new branch how to#

Also to keep a personal local branch, we can also have a purpose/task driven name such as “MyLocalBranch” or a branch with a reference number, etc. In order to keep up with these commonly used phases we can have branches release/DEV, release/QA, master (PROD). The following screenshot shows some of these branches used in a typical environment. We should also note that when operations team notice any issues with the applications running at production, they might refer back to the developers, which will again trigger another set of development, quality analysis and production phases. There could be few more additional stages in this type of work flow, but the DEV, QA and PROD are the most commonly used ones. Once testing is completed, it can move to pre-production (PREPROD) phase and then finally to the production (PROD) phase which is the final destination of the project where it accomplishes its intended purpose. Usually a project starts at the development (DEV) phase, then goes to quality analysis (QA or testing) phase. This would keep the work flow streamlined into the different stages a project goes through. development environment with multiple users are working together, it would be better to keep multiple branches. Once they are done with their updated files, they can stage, commit and push it to remote branch. This branch can be shared with other users so that they can also clone the repository and do their work in their machines. For that we used a single branch called “master” locally and a branch called “origin/master” remotely.

Sourcetree checkout a new branch how to#

In the previous post, we showed how to synchronize the local repository with the remote repository located at Bitbucket cloud.