-
Notifications
You must be signed in to change notification settings - Fork 677
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag '3.0.0.0.0' into clarity-wasm-3-0-0-0
- Loading branch information
Showing
55 changed files
with
1,348 additions
and
1,105 deletions.
There are no files selected for viewing
This file contains 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
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains 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 file contains 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 file contains 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 file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Git Branching | ||
|
||
The following is a slightly modified version of the gitflow branching strategy described in <https://nvie.com/posts/a-successful-git-branching-model/> | ||
|
||
## Main Branches | ||
|
||
- **master** - `master` is the main branch where the source code of HEAD always reflects a production-ready state. | ||
- **develop** - `develop` is the branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release. | ||
- **next** - `next` may contain consensus-breaking changes for a future release. | ||
- **release/X.Y.Z.A.n** is the release branch. | ||
|
||
When the source code in the develop branch reaches a stable point and is ready to be released, a release branch is created as `release/X.Y.Z.A.n` (see [release-process.md](./release-process.md)). | ||
After release, the following will happen: | ||
|
||
- `release/X.Y.Z.A.n` branch is merged back to `master`. | ||
- `master` is then merged into `develop`, and development continues in the `develop` branch. | ||
- `develop` is then merged into `next`. | ||
|
||
## Supporting Branches | ||
|
||
Branch names should use a prefix that conveys the overall goal of the branch. | ||
All branches should be based off of `develop`, with the exception being a hotfix branch which may be based off of `master`. | ||
|
||
- `feat/some-fancy-new-thing`: For new features. | ||
- `fix/some-broken-thing`: For hot fixes and bug fixes. | ||
- `chore/some-update`: Any non code related change (ex: updating CHANGELOG.md, adding comments to code). | ||
- `docs/something-needs-a-comment`: For documentation. | ||
- `ci/build-changes`: For continuous-integration changes. | ||
- `test/more-coverage`: For branches that only add more tests. | ||
- `refactor/formatting-fix`: For refactors of the codebase. | ||
|
||
The full branch name **must**: | ||
|
||
- Have a maximum of 128 characters. | ||
- Only includes ASCII lowercase and uppercase letters, digits, underscores, periods and dashes. |
Oops, something went wrong.