From ae2b0266dd9f74343944827d736bf3bb86cee792 Mon Sep 17 00:00:00 2001 From: Robert Sese Date: Fri, 11 Mar 2022 16:35:16 -0600 Subject: [PATCH] Add note about doing step 7 as soon as you can (#26128) * Add note about doing step 7 as soon as you can * Be super explicit about doing this step asap --- .../enterprise-server-issue-templates/deprecation-issue.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/actions-scripts/enterprise-server-issue-templates/deprecation-issue.md b/.github/actions-scripts/enterprise-server-issue-templates/deprecation-issue.md index 23157ee460..878852ba41 100644 --- a/.github/actions-scripts/enterprise-server-issue-templates/deprecation-issue.md +++ b/.github/actions-scripts/enterprise-server-issue-templates/deprecation-issue.md @@ -78,3 +78,5 @@ In your `docs-internal` checkout: - [ ] In `github/github`, edit the release's config file in `app/api/description/config/releases/`, and change `deprecated: false` to `deprecated: true`. - [ ] Open a new PR, and get the required code owner approvals. A docs-content team member can approve it for the docs team. - [ ] When the PR is approved, [deploy the `github/github` PR](https://thehub.github.com/engineering/devops/deployment/deploying-dotcom/). If you haven't deployed a `github/github` PR before, work with someone that has -- the process isn't too involved depending on how you deploy, but there are a lot of details that can potentially be confusing as you can see from the documentation. + +**Note**: you can do this step independently of the other steps after a GHES version is deprecated since it should no longer get updates in github/github. You should plan to get this PR merged as soon as possible, otherwise if you wait too long our OpenAPI automation may re-add the static files that you removed in step 5.