Naming conventions for Branches

Your branch name syntax can be similar to something like this:

name/issue#/description

Here name may be Your Github Id or your initial name, issue denotes the issue number and a very short description about the branch

Example: 

dora/45/new-feature

You can also consider this naming convention:

A. If it’s a new feature

feature/name/issue#    

B. If branch is for fixing new bug

bug/name/issue#                

Example:

new-footer/dora/251

Git Workflow Etiquettes

Version control systems like Git have revolutionized the way developers collaborate on projects. However, efficient collaboration depends on sticking to certain manners that streamline the workflow and ensure code quality. Here are some important Git workflow etiquettes to follow.

Table of Content

  • 1. Naming conventions for Branches
  • 2. Etiquettes for Git Commit Messages
  • 3. Pull Request Guidelines

Similar Reads

1. Naming conventions for Branches

Your branch name syntax can be similar to something like this:...

2. Etiquettes for Git Commit Messages

Having proper commit messages helps in increasing the readability of git logs and file history. One may consider naming your commit messages in the following categories:...

3. Pull Request Guidelines

When Opening a Pull Request, do consider adding the following points in the message...