Skip to content

Commit f361d5a

Browse files
rachmarirachmari
authored
update release steps (github#36642)
1 parent fcba180 commit f361d5a

File tree

4 files changed

+19
-197
lines changed

4 files changed

+19
-197
lines changed

‎.github/actions-scripts/enterprise-server-issue-templates/release-issue.md‎

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,18 +18,29 @@ If you aren't comfortable going through the steps alone, sync up with a docs eng
1818
```
1919
script/update-enterprise-dates.js
2020
```
21-
- [ ] Create REST files based on previous version. Copy the latest GHES version of the decorate file from `src/rest/data` to a new file in the same directory for the new GHES release. Ex, `cp src/rest/data/ghes-3.4.json src/rest/data/ghes-3.5.json`.
21+
- [ ] Create REST files based on previous version. Copy the latest GHES release data to a new directory for new release. For example, if the current release is 3.8 and the new release is 3.9:
22+
```
23+
cp -rf src/rest/data/ghes-3.8 src/rest/data/ghes-3.9
24+
```
2225
23-
- [ ] Create GraphQL files based on previous version:
26+
- [ ] Create GraphQL files based on previous version. Copy the latest GHES release data to a new directory for new release. For example, if the current release is 3.8 and the new release is 3.9:
2427
2528
```
26-
script/enterprise-server-releases/create-graphql-files.js --oldVersion <PLAN@RELEASE> --newVersion <PLAN@RELEASE>
29+
cp -rf src/graphql/data/ghes-3.8 src/graphql/data/ghes-3.9
30+
cp -rf data/graphql/ghes-3.8 data/graphql/ghes-3.9
2731
```
28-
- [ ] Create webhook files based on previous version:
32+
- [ ] Create webhook files based on previous version. Copy the latest GHES release data to a new directory for new release. For example, if the current release is 3.8 and the new release is 3.9:
2933
3034
```
31-
script/enterprise-server-releases/create-webhook-files.js --oldVersion <PLAN@RELEASE> --newVersion <PLAN@RELEASE>
35+
cp -rf src/webhooks/data/ghes-3.8 src/webhooks/data/ghes-3.9
3236
```
37+
38+
- [ ] Create GitHub App files based on previous version. Copy the latest GHES release data to a new directory for new release. For example, if the current release is 3.8 and the new release is 3.9:
39+
40+
```
41+
cp -rf src/github-apps/data/ghes-3.8 src/github-apps/data/ghes-3.9
42+
```
43+
3344
- [ ] Create a placeholder release notes file called `data/release-notes/<PRODUCT>/<RELEASE NUMBER>/PLACEHOLDER.yml`. For example `data/release-notes/enterprise-server/3-1/PLACEHOLDER.yml`. Add the following placeholder content to the file:
3445
3546
**Note:** All of the content in this file will be updated when the release notes are created in the megabranch including the filename `PLACEHOLDER.yml`. You can update the date or leave it as-is and wait to update it when the release notes are finalized.
@@ -243,6 +254,7 @@ If you aren't comfortable going through the steps alone, sync up with a docs eng
243254

244255
```
245256
script/enterprise-server-releases/release-banner.js --action create --version <PLAN@RELEASE>
257+
script/copy-fixture-data.js // This updates the fixtures to match the updated data/variables/release_candidate.yml file
246258
```
247259

248260
- [ ] Create a PR with the above changes. This PR is used to track all docs changes and smoke tests associated with the release. For example https://github.com/github/docs-internal/pull/22286.

‎script/enterprise-server-releases/create-graphql-files.js‎

Lines changed: 0 additions & 114 deletions
This file was deleted.

‎script/enterprise-server-releases/create-webhook-files.js‎

Lines changed: 0 additions & 76 deletions
This file was deleted.

‎tests/fixtures/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,9 @@ ROOT=tests/fixtures jest tests/rendering-fixtures/
5858

5959
### Exceptions
6060

61-
The top-level product names in the fixture content needs to be a pefect
61+
The top-level product names in the fixture content needs to be a perfect
6262
subset of the product names in the real content. That's because they
63-
get compiled in to the Next rewrite functionalty so we can support
63+
get compiled in to the Next rewrite functionality so we can support
6464
URLs that actually are `free-pro-team@latest` without mentioning it in
6565
the URL.
6666

0 commit comments

Comments
 (0)