You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ Then, the `release` workflow handles everything:
80
80
### Regular flow
81
81
82
82
1. Create [feature branch](#conventions)
83
-
2. Make changes in your feature branch and [commit](#conventions)
83
+
2. Make changes in your feature branch and [commit](#conventions) using `yarn commit`
84
84
3. Create a Pull Request from your feature branch to `main`
85
85
The PR is needed to test the code before pushing to release branch
86
86
4. If your PR contains breaking changes, don't forget to put a `BREAKING CHANGES` label
@@ -92,24 +92,28 @@ Then, the `release` workflow handles everything:
92
92
1. Assume your prerelease tag is `beta`
93
93
2. Create `release/beta` branch
94
94
3. Create [feature branch](#conventions)
95
-
4. Make changes in your feature branch and [commit](#conventions)
95
+
4. Make changes in your feature branch and [commit](#conventions) using `yarn commit`
96
96
5. Create a Pull Request from your feature branch to `release/beta`
97
97
The PR is needed to test the code before pushing to release branch
98
98
6. Create Github release with tag like `v1.0.0-beta`, pointing to `release/beta` branch
99
-
For next `beta` versions use semver build syntax: `v1.0.0-beta+1`
99
+
For next `beta` versions use semver build syntax: `v1.0.0-beta+1`
100
100
7. After that, the `release` workflow will publish your package with the `beta` tag
101
101
8. When the `beta` version is ready to become `latest` - create a Pull Request from `release/beta` to `main` branch
102
102
9. Continue from the [Regular flow's](#regular-flow)#5 step
103
103
104
104
### Conventions
105
105
106
106
**Feature branches**:
107
+
107
108
- Should start with `feat/`, `fix/`, `docs/`, `refactor/`, and etc., depending on the changes you want to propose (see [pr-labeler.yml](./.github/pr-labeler.yml) for a full list of scopes)
108
109
109
110
**Commits**:
111
+
112
+
- Should be created using `yarn commit` command
110
113
- Should follow the [Conventional Commits specification](https://www.conventionalcommits.org)
111
114
112
115
**Pull requests**:
116
+
113
117
- Should have human-readable name, for example: "Add a TODO list feature"
114
118
- Should describe changes
115
119
- Should have correct labels
@@ -148,4 +152,4 @@ Then, the `release` workflow handles everything:
148
152
149
153
### The last step
150
154
151
-
Remove **Using Template** section from README (don't forget about Navigation links)
155
+
Remove **Using Template** section from README (don't forget about Navigation links)
0 commit comments