BranchesPolicy
English | Japanese
| < Abbreviated notation for custom key type's definitions || Branches Policy | Versioning Policy > |
- Dancing☆Onigiri (CW Edition) is managed by multiple branches.
- Release-only branch. Except for commit errors, releases are made from this branch. No merging into the master branch from any branch other than the develop branch.
- The branch from which other branches are merged. Contributors and maintainers will submit pull requests to this branch. As a general rule, direct commits from this branch are only done to increase the version number.
- This is the default branch to avoid merging mistakes. This is the branch just before a release, but sometimes the fixes are not completed. If you use resources from this branch, please use them with the understanding that they are pre-release.
- Maintenance branch for past versions. Past versions do not add functionality, only related fixes to bugs fixed in the latest version. No merging from this branch to other branches.
- Development branch. There are no specific rules, but when an administrator submits a PR, the branch will be cut according to the following rules.
- All branches are generated from the develop branch, so there is no distinction between them.
| Type | Summary |
|---|---|
| feature/* | Branches created when adding or improving functionality |
| hotfix/* | Branches created for bug fixes |
| chore/* | Branches created when fixing things that do not affect functionality, such as readme, various template fixes, etc. |
| < Abbreviated notation for custom key type's definitions || Branches Policy | Versioning Policy > |