-
Notifications
You must be signed in to change notification settings - Fork 40
Naming your branches
Luca Martial edited this page Apr 25, 2023
·
6 revisions
When attacking an issue, the new branch you create should be named either:
- If it's a fix:
fix/couple-words-describing-issue
- If it's a feature:
feature/couple-words-describing-feature
- If it's a chore:
chore/couple-words-describing-chore
For example, issue #20 was created to rename a parameter in the noisy label testing function to something more descriptive. The branch name would be chore/rename-k-param
.
When preparing a release, use the following name (change the version number): release/0.0.1