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-loginchore/update-dependenciesRelated terms
- branch — In Git, a movable name for one commit; committing on the branch moves the name forward to the new commit.
- feature branch — A branch made for one piece of work, such as a feature or bug fix, and merged back when that work is done.
- GitHub issue — A numbered item on GitHub for tracking a bug, task or feature request, with its own discussion.
Taught in
- Installing Git, And Telling It Who You Are — Advanced Git Internals & Distributed Workflows
- A Repository Is A Folder With A Memory — Advanced Git Internals & Distributed Workflows
- A Branch Is A Moving Pointer — Advanced Git Internals & Distributed Workflows
- HEAD, And Why Detached HEAD Is Not An Error — Advanced Git Internals & Distributed Workflows
- The Pull Request, And Branch Naming — Advanced Git Internals & Distributed Workflows
- Resolving A Conflict, Line By Line — Advanced Git Internals & Distributed Workflows
- Tags And Releases — Advanced Git Internals & Distributed Workflows