

Team members can create and delete these branches whenever it is required. It ensures a stable codebase for the production environment through the QA testing process. This branch holds the QA codes and automation testing of the implemented changes.
#RENAME GIT BRANCH CODE#
Merging is possible only after code review.

It usually is stable and doesn't allow direct check-in. Team members need to keep the master branch stable and updated. The Master branch is the default branch available in the Git repository. Before merging to the master, changes made in the dev branch undergo reviews and tests. The two broad categories of Git branchesĪvailable permanently in the repository, the naming convention of regular branches is easy and straightforward.ĭevelopment (Dev) Dev, the main development branch, restricts developers from adding any changes in the master branch directly. It helps in separating the work strategically. Git branching naming convention supports the organic growth of a codebase in a systematic way. With a lack of appropriate naming conventions, the code maintenance team suffers numerous confusions and complications. It helps teams and developers by describing the naming guidelines of branches and elaborates on what use the branches should have, and so on. #19- 14 Patterns to Ace Any Coding Interview QuestionĪ branching strategy is a convention or a set of rules that specify when branches get created.
#RENAME GIT BRANCH HOW TO#

