@@ -27,7 +27,7 @@ Before submitting your contribution though, please make sure to take a moment an
2727
2828Before submitting a pull request, please make sure the following is done:
2929
30- 1 . Fork the repository and create your branch from ` main ` .
30+ 1 . Fork the repository and create your branch from ` v1 ` .
31311 . Run ` npm install ` in the repository root.
32321 . If you’ve fixed a bug or added code that should be tested, don't forget to add [ tests] ( #tests ) !
33331 . Ensure the test suite passes (see the [ Tests section] ( #tests ) for more details).
@@ -251,22 +251,22 @@ We use [Changesets](https://github.com/changesets/changesets) flow.
251251After merging a PR with a changeset, the release PR is automatically created.
252252
253253If the pipelines are not starting, close and reopen the PR.
254- Merging that PR triggers the release process.
254+ Merging that PR triggers the release process under the ` v1 ` label .
255255
256256### Revert a release
257257
258258There's no possibility to revert a release itself.
259259However, you can release a new version with a problematic commit reverted.
260- Create a new branch from ** main ** , then find the hash of the commit you want to revert and run ` git revert <commit-hash> ` .
260+ Create a new branch from ** v1 ** , then find the hash of the commit you want to revert and run ` git revert <commit-hash> ` .
261261Create a patch-level changeset for the revert and open a PR with it.
262262Merge the PR and cut a release according to the [ Release flow] ( #release-flow ) .
263263
264264### Snapshot release
265265
266266To release an experimental version to the ** NPM** registry, follow these steps:
267267
268- 1 . Create a new PR to ** main ** .
269- 2 . Add the ` snapshot ` label to the PR. This creates a new PR with to the ` snapshot ` branch (which is a copy of the ` main ` branch).
270- 3 . Merging the second PR triggers release to the ** NPM** registry under the ` snapshot ` tag.
268+ 1 . Create a new PR to ** v1 ** .
269+ 2 . Add the ` snapshot ` label to the PR.
270+ This triggers a release of the current branch changes to the ** NPM** registry under the ` snapshot ` tag.
271271
272- The released version can be installed with ` npm install @redocly/cli@snapshot ` .
272+ The released version can be installed with ` npm install @redocly/cli@snapshot `
0 commit comments