Skip to content

Commit 56232fa

Browse files
committed
docs: remove reference to check gh assets
1 parent 8aa4230 commit 56232fa

File tree

3 files changed

+5
-7
lines changed

3 files changed

+5
-7
lines changed

.github/PULL_REQUEST_TEMPLATE/release_template.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,5 @@ Follow "Publishing a release" steps in `ci/README.md`
1212

1313
<!-- Note some of these steps below are redundant since they're listed in the "Publishing a release" docs -->
1414

15-
- [ ] double-check github release tag is the commit with artifacts (_note gets messed up after uploading assets_)
1615
- [ ] publish release and merge PR
1716
- [ ] update the AUR package

ci/README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,14 +24,13 @@ Any file or directory in this subdirectory should be documented here.
2424
- It will upload them to the draft release.
2525
6. Run some basic sanity tests on one of the released packages.
2626
- Especially make sure the terminal works fine.
27-
7. Make sure the github release tag is the commit with the artifacts.
28-
8. Publish the release and merge the PR.
27+
7. Publish the release and merge the PR.
2928
1. CI will automatically grab the artifacts and then:
3029
1. Publish the NPM package from `npm-package`.
3130
2. Publish the Docker Hub image from `release-images`.
32-
9. Update the AUR package.
31+
8. Update the AUR package.
3332
- Instructions on updating the AUR package are at [cdr/code-server-aur](https://github.com/cdr/code-server-aur).
34-
10. Wait for the npm package to be published.
33+
9. Wait for the npm package to be published.
3534

3635
## dev
3736

docs/MAINTAINING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
- [Project Boards](#project-boards)
1010
- [Versioning](#versioning)
1111
- [Release](#release)
12-
- [Release Manager Rotation](#release-manager-rotation)
12+
- [Release Manager Rotation](#release-manager-rotation)
1313

1414
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
1515

@@ -68,7 +68,7 @@ The code-server project follows traditional [semantic versioning](ttps://semver.
6868

6969
## Release
7070

71-
## Release Manager Rotation
71+
### Release Manager Rotation
7272

7373
With each release, we rotate the role of "release manager" to ensure every maintainer goes through the process. This helps us keep documentation up-to-date and encourages us to continually review and improve the flow with each set of eyes.
7474

0 commit comments

Comments
 (0)