- The
mainbranch should be kept stable for potential releases. - Create a
developbranch for ongoing development and set it as the default branch. - For adding a feature, create a branch starting with
feat/(e.g.,feat/feature-name) from thedevelopbranch. - For fixing an issue, create a branch starting with
fix/(e.g.,fix/feature-name,fix/issue-name) from thedevelopbranch. - For refactoring code, create a branch starting with
ref/(e.g.,ref/feature-name,ref/v1.0.0) from thedevelopbranch. - For release, create a branch starting with
release/(e.g.,release/v1.0.0) from thedevelopbranch. - Once the release branch is ready, merge it to the
mainbranch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // this line is added to create a gist. Empty file is not allowed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Gist 4 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Gist 2 |