-
Notifications
You must be signed in to change notification settings - Fork 2
branch_naming_convention
Jkutkut edited this page Jun 3, 2023
·
1 revision
Branches should be named in the following way:
-
Branch type first, followed by a hyphen (-):
-
dev
Branches containing big feature changes. They should belong to one person, and should be linked to an issue. -
wip
Work in progress branches. This may include small changes affecting thedev
ones. They should be used, only when an auxiliary branch is needed (ie: unstable changes for a givendev
branch). -
rel
Unique release branch, the one where everything should work.
-
-
Feature identifier (snake_case): What will this branch bring to the project