Branch Naming Convention

Branch Naming

Branches being created should have the following format:

<story type>/<3-4 word story description>

Example

chore/save-the-world

The story type indicates the context of the branch and should be written in full and with lowercase letters:

feature for tasks that add immediate, actionable value to the user. Are mostly functionalities. e.g add signup functionalities

chore for tasks are useful to the developer but not the users of the app. e.g Writing tests

bug for bug fix branches.

release for pull requests that are to be merged to production

The <3-4 word story description> is a summary of the purpose of the branch. It is delimited with a hyphen (-).

For example, travis-ci-setup