Skip to content

Commit 0a522b2

Browse files
authored
Update RELEASE_INSTRUCTIONS.md
1 parent 26fcc4d commit 0a522b2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

RELEASE_INSTRUCTIONS.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
5. Run `git push -u origin <new branch name>` to push the version changes to your branch.
88
6. Make a new PR against the base repository containing your version changes.
99
7. Have someone at High Fidelity merge the PR.
10-
2. Make a Pull Request to pull all of the code from the `main` branch **of your fork** into the `release` branch.
11-
- If you followed the instructions from step (1) above, you can make a pull request with a base of `main` and a compare branch of `<new branch name>`.
10+
2. Make a Pull Request to pull all of the code from the `main` branch, **including the new version changes**, into the `release` branch.
11+
- If you followed the detailed instructions from step (1) above, you can make a pull request with a base of `main` and a compare branch of `<new branch name>`.
1212
3. Have the PR reviewed and merged.
1313
4. Once the PR is merged and the latest code is now on the `release` branch, [click here to start drafting a new release](https://github.com/highfidelity/hifi-spatial-audio-js/releases/new).
1414
5. Under "Tag version", input `v<Package Version>`

0 commit comments

Comments
 (0)