-
Notifications
You must be signed in to change notification settings - Fork 40
Naming your branches
Luca Martial edited this page Jan 31, 2023
·
6 revisions
When attacking an issue, the new branch you create should be named issue/[the GH issue number]-couple-words-describing-issue. If it's a feature: feature/[the GH issue number]-couple-words-describing-issue
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 issue/20-rename-k-param.
When preparing a release, use the following name (change the version number): release-0.0.1