@@ -14,7 +14,7 @@ have been merged since the last release have been labeled with the appropriate
1414represent something that would make sense to our users. Some great information
1515on why this is important can be found at
1616[ keepachangelog.com] ( https://keepachangelog.com/en/1.0.0/ ) , but the overall
17- guiding principles here is that changelogs are for humans, not machines.
17+ guiding principle here is that changelogs are for humans, not machines.
1818
1919When reviewing merged PR's the labels to be used are:
2020
@@ -30,12 +30,33 @@ When reviewing merged PR's the labels to be used are:
3030
3131Once the prep work is completed, the actual release is straight forward:
3232
33+ * First, ensure that you have installed your projects dependencies:
34+
3335```
3436yarn install
35- yarn release
3637```
3738
38- The ` release ` script leverages
39- [ release-it] ( https://github.com/release-it/release-it/ ) to do the mechanical
40- release process. It will prompt you through the process of choosing the version
41- number, tagging, pushing the tag and commits, etc.
39+ * Second, ensure that you have obtained a
40+ [ GitHub personal access token] [ generate-token ] with the ` repo ` scope (no
41+ other permissions are needed). Make sure the token is available as the
42+ ` GITHUB_AUTH ` environment variable.
43+
44+ For instance:
45+
46+ ``` bash
47+ export GITHUB_AUTH=abc123def456
48+ ```
49+
50+ [ generate-token ] : https://github.com/settings/tokens/new?scopes=repo&description=GITHUB_AUTH+env+variable
51+
52+ * And last (but not least 😁) do your release.
53+
54+ ```
55+ npx release-it
56+ ```
57+
58+ [ release-it] ( https://github.com/release-it/release-it/ ) manages the actual
59+ release process. It will prompt you to to choose the version number after which
60+ you will have the chance to hand tweak the changelog to be used (for the
61+ ` CHANGELOG.md ` and GitHub release), then ` release-it ` continues on to tagging,
62+ pushing the tag and commits, etc.
0 commit comments