branch naming convention

A team agreement on how branches are named, usually a category, an issue number and a short lowercase description joined by hyphens.

In more detail

Names such as feature/123-add-login or bugfix/456-fix-header say at a glance what a branch is for and link it to its issue. Git accepts almost any name, so consistency comes only from the convention.

Examples

feature/123-add-login
chore/update-dependencies

Related terms

Taught in

References