Ghes release automation pipelines (#36748)

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>

data/release-notes/PLACEHOLDER-TEMPLATE.yml

@@ -0,0 +1,200 @@
+date: '2099-12-31'
+release_candidate: true
+deprecated: false
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can’t upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  # Remove section heading if the section contains no notes.
+
+  features:
+    # Remove a sub-section heading if the heading contains no notes. If sections
+    # that regularly recur are missing, add placeholders to this template.
+
+    - heading: Instance administration
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Instance services
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Identity and access management
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Authentication
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Migrations
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Policies
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Audit logs
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Connect
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Advanced Security
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Dependabot
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Code security
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Actions
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Packages
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Pages
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Community experience
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Organizations
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Repositories
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Issues
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Projects
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Discussions
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Commits
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Pull requests
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Releases
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Gist
+      notes:
+        # LINK TO RELEASES ISSUE
+        - |
+          ...
+
+    - heading: Markdown
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Accessibility
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: GitHub Mobile
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+    - heading: Integrations and extensions
+      notes:
+        # LINK TO RELEASE ISSUE
+        - |
+          ...
+
+  changes:
+    # LINK TO RELEASE ISSUE
+    - |
+      ...
+
+  known_issues:
+    # INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB
+    - |
+      ...
+
+  deprecations:
+    # LINK TO RELEASE ISSUE
+    - |
+      ...

src/automated-pipelines/lib/config.json

@@ -0,0 +1,9 @@
+{
+  "automation-pipelines": [
+    "codeql-cli",
+    "github-apps",
+    "graphql",
+    "rest",
+    "webhooks"
+  ]
+}

src/ghes-releases/lib/deprecation-steps.md

@@ -119,9 +119,8 @@ Poke around several pages, ensure that the stylesheets are working properly, ima
 
 **Note:** We do not remove the old content for GHES release notes. New release notes can be added after we perform a deprecation in some rare cases, and not removing this content makes it easier for us to re-scrape the content to add to Azure Blob Storage.
 
-- [ ] In your `docs-internal` checkout, create a new branch `remove-<version>-static-files` branch: `git checkout -b remove-<version>-static-files` (you can branch off of `main` or from your `deprecate-<version>` branch, up to you).
-- [ ] Run `src/ghes-releases/scripts/remove-static-files.js` and commit results.
-- [ ] Re-generate the static files by running `src/rest/scripts/update-files.js --decorate-only`.
+- [ ] In your `docs-internal` checkout, create a new branch: `git checkout -b remove-<version>-data-files` (you can branch off of `main` or from your `deprecate-<version>` branch, up to you).
+- [ ] Run `src/ghes-releases/scripts/sync-automated-pipeline-data.js` and commit results.
 - [ ] Open a new PR.
 - [ ] Get a review from docs-engineering and merge. This step can be merged independently from step 6. The purpose of splitting up steps 5 and 6 is to focus the review on specific files.