Some examples of such Git branch names are :īug-header-size-issue - The developer is trying to fix the header-size bug. Some group words used are Bug, Hotfix, or WIP(work in progress) which makes all the developers get an idea of what the branch is meant for. The branch name should start with a group word that signifies the purpose of the branch. Some naming conventions generally followed by developers are : Start Branch Name with Group Word They can be classified into the following branches

They are not present permanently in the repository. Temporary Git branches are the branches that are created and deleted as per requirement. QA branch or the test ranch is used for QA testing and automation testing before merging any code to production.The Master branch should be stable every time and before any merging, any code from the dev branch to the master branch must undergo rigorous testing and verification. The master branch is the life of the production branch which is deployed to production. Master branch is the default branch in the Git repository.When the code in the dev branch undergoes reviews and testing then only it is merged into the master branch. The developers can not directly write code in the master branch as the master branch is the production branch. Dev branch is the development branch that is used by developers to develop any new feature.These can be further classified into three categories namely Dev branch, master branch, and QA branch or test branch. Regular Git branches are those branches that are permanently available in your repositories. Git branches are broadly classified into two categories : Git provides flexible branching strategies which help in the separation of work. Some naming conventions are being followed by the developers while creating a new branch that helps in avoiding confusion and maintaining the codebase by the code maintenance team. Developers need to create a new branch for every feature. While working in a large codebase developers have to work on independent features. This naming convention helps the developer to get an overview of what is the purpose of the particular branch without getting into the code inside that branch. listing branches that e.g.Git branch naming conventions are the set of rules which are followed by the developers while creating and naming any branch.deleting existing local or remote branches.The 'git branch' command is used for a variety of tasks: The '-u' flag tells Git to establish a 'tracking connection', which will make pushing and pulling much easier in the future.

If you want to name the local branch like the remote one, you only have to specify the remote branch's name: $ git checkout -track origin/ How do I create a new branch in a remote repository?Īfter working on your new local branch for some time, you might want to publish it in your remote repository, to share it with your team: $ git push -u origin To take a remote branch as the basis for your new local branch, you can use the '-track' option: $ git branch -track origin/Īlternatively, you can also use the 'checkout' command to do this. You can also base your new branch on a specific tag you already have in your repository: $ git branch v1.2 How do I create a new branch from a remote branch? If you want to start your new branch based on a specific commit (not a branch), then you can provide the commit hash as the starting point: $ git branch f71ac24d How do I create a new branch from a specific tag? How do I create a new branch from a specific commit? You can learn more about Tower's drag and drop capabilities by clicking here. If you're using the Tower Git client, you can simply use drag and drop to create new branches (and to merge, cherry-pick, etc.): If you want to base your new branch on a different existing branch, simply add that branch's name as a starting point: $ git branch To create a new branch that is based on your currently checked out (HEAD) branch, simply use 'git branch' with the name of the new branch as the only parameter: $ git branch How do I create a new branch based on some existing one? How do I create a new branch based on the current HEAD? There are a couple of different use cases when creating branches in Git. In fact, the power and flexibility of its branching model is one of the biggest advantages of Git! Git makes creating and managing branches very easy.