repo sync

.eslintrc.js

@@ -13,7 +13,7 @@ module.exports = {
     babelOptions: { configFile: './.babelrc' },
     sourceType: 'module',
   },
-  ignorePatterns: ['tmp/*'],
+  ignorePatterns: ['tmp/*', '!/.*', '/.next/'],
   rules: {
     'import/no-extraneous-dependencies': ['error', { packageDir: '.' }],
   },

.github/actions-scripts/fr-add-docs-reviewers-requests.js

@@ -134,8 +134,8 @@ async function run() {
   // Exclude existing items going forward.
   // Until we have a way to check from a PR whether the PR is in a project,
   // this is how we (roughly) avoid overwriting PRs that are already on the board
-  let newItemIDs = []
-  let newItemAuthors = []
+  const newItemIDs = []
+  const newItemAuthors = []
   itemIDs.forEach((id, index) => {
     if (!existingItemIDs.includes(id)) {
       newItemIDs.push(id)

.github/actions-scripts/ready-for-docs-review.js

@@ -85,8 +85,8 @@ async function run() {
     // - affected docs sets (not considering changes to data/assets)
     let numFiles = 0
     let numChanges = 0
-    let features = new Set([])
-    const files = data.item.files.nodes.forEach((node) => {
+    const features = new Set([])
+    data.item.files.nodes.forEach((node) => {
       numFiles += 1
       numChanges += node.additions
       numChanges += node.deletions

.github/workflows/browser-test.yml

@@ -6,9 +6,6 @@ name: Browser Tests
 
 on:
   workflow_dispatch:
-  push:
-    branches:
-      - main
   pull_request:
     paths:
       - '**.js'
@@ -56,7 +53,7 @@ jobs:
         uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
         with:
           path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}-${{ hashFiles('.github/workflows/browser-test.yml') }}
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
 
       - name: Cache lib/redirects/.redirects-cache_en_ja.json
         uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353

.github/workflows/check-all-english-links.yml

@@ -34,6 +34,11 @@ jobs:
           cache: npm
       - name: npm ci
         run: npm ci
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
       - name: npm run build
         run: npm run build
       - name: Run script

.github/workflows/code-lint.yml

@@ -18,6 +18,7 @@ on:
       - '**.yaml'
       - '**.yml'
       - '**.scss'
+      - .eslintrc.js
       # In case something like eslint or tsc or prettier upgrades
       - 'package-lock.json'
       # Ultimately, for debugging this workflow itself

.github/workflows/enterprise-release-sync-search-index.yml

@@ -57,6 +57,12 @@ jobs:
         id: getVersion
         run: $GITHUB_WORKSPACE/.github/actions-scripts/enterprise-search-label.js
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Generate the search index files
         if: ${{ steps.getVersion.outputs.versionToSync }}
         env:

.github/workflows/link-check-dotcom.yml

@@ -32,6 +32,12 @@ jobs:
       - name: Install
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Build
         run: npm run build
 

.github/workflows/link-check-ghae.yml

@@ -32,6 +32,12 @@ jobs:
       - name: Install
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Build
         run: npm run build
 

.github/workflows/link-check-ghec.yml

@@ -30,6 +30,12 @@ jobs:
       - name: Install
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Build
         run: npm run build
 

.github/workflows/link-check-ghes.yml

@@ -32,6 +32,12 @@ jobs:
       - name: Install
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Build
         run: npm run build
 

.github/workflows/pa11y.yml

@@ -29,6 +29,12 @@ jobs:
       - name: Install dependencies
         run: npm ci --include=optional
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Run build scripts
         run: npm run build
 

.github/workflows/ping-staging-apps.yml

@@ -27,7 +27,5 @@ jobs:
           cache: npm
       - name: npm ci
         run: npm ci
-      - name: npm run build
-        run: npm run build
       - name: Run script
         run: script/ping-staging-apps.js

.github/workflows/repo-sync.yml

@@ -21,7 +21,7 @@ on:
     - cron: '10,40 * * * *' # every 30 minutes
 
 permissions:
-  contents: read
+  contents: write
   pull-requests: write
 
 jobs:

.github/workflows/staging-build-and-deploy-pr.yml

@@ -33,7 +33,7 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  build-and-deploy:
+  build-and-deploy-pr:
     # Important. This whole file is only supposed to run in the PRIVATE repo.
     if: ${{ github.repository == 'github/docs-internal' }}
 

.github/workflows/staging-build-pr.yml

@@ -13,16 +13,6 @@ on:
       - reopened
       - synchronize
 
-  # This is necessary so that the cached things can be reused between
-  # pull requests.
-  # If we don't let the workflow run on `main` the caching will only
-  # help between multiple runs of the same workflow. By letting
-  # it build on pushes to main too, the cache will be reusable
-  # in other people's PRs too.
-  push:
-    branches:
-      - main
-
 permissions:
   contents: read
 
@@ -97,7 +87,7 @@ jobs:
         uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
         with:
           path: .next/cache
-          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}-${{ hashFiles('.github/workflows/staging-build-pr.yml') }}
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
 
       - name: Build
         run: npm run build
@@ -112,8 +102,6 @@ jobs:
         run: npm set-script heroku-postbuild "echo 'Application was pre-built!'"
 
       - name: Create an archive
-        # Only bother if this is actually a pull request
-        if: ${{ github.event.pull_request.number }}
         run: |
           tar -c --file=app.tar \
             node_modules/ \
@@ -143,8 +131,6 @@ jobs:
       # We are not willing to trust the rest (e.g. script/) for the remainder
       # of the deployment process.
       - name: Upload build artifact
-        # Only bother if this is actually a pull request
-        if: ${{ github.event.pull_request.number }}
         uses: actions/upload-artifact@27121b0bdffd731efa15d66772be8dc71245d074
         with:
           name: pr_build

.github/workflows/sync-search-indices.yml

@@ -64,6 +64,12 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Run build scripts
         run: npm run build
 

.github/workflows/sync-search-pr.yml

@@ -32,6 +32,12 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - name: Build
         run: npm run build
 

.github/workflows/test-windows.yml

@@ -53,6 +53,12 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
+      - name: Cache nextjs build
+        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        with:
+          path: .next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
+
       - if: ${{ github.repository == 'github/docs-internal' }}
         name: Clone early access
         run: npm run heroku-postbuild

components/page-header/RestRepoBanner.tsx

@@ -18,7 +18,7 @@ const restRepoCategoryExceptionsTitles = {
   collaborators: 'Collaborators',
   commits: 'Commits',
   deployments: 'Deployments',
-  pages: 'Github Pages',
+  pages: 'GitHub Pages',
   releases: 'Releases',
   'repository-metrics': 'Repository metrics',
   webhooks: 'Webhooks',
@@ -35,10 +35,12 @@ export const RestRepoBanner = () => {
     keyof typeof restRepoCategoryExceptionsTitles
   >
   const newRestPagesText = pages.map((page, i) => [
-    <Link href={`/${router.locale}/rest/reference/${page}`}>
-      {restRepoCategoryExceptionsTitles[page]}
+    <>
+      <Link href={`/${router.locale}/rest/reference/${page}`}>
+        {restRepoCategoryExceptionsTitles[page]}
+      </Link>
       {i < pages.length - 1 && ', '}
-    </Link>,
+    </>,
   ])
 
   return (

content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md

@@ -34,15 +34,19 @@ To configure a connection, your proxy configuration must allow connectivity to `
 
 After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as unified search and unified contributions. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)."
 
-When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection:
+When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, or enable {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection:
 {% ifversion ghes %}
 - The public key portion of your {% data variables.product.prodname_ghe_server %} license
 - A hash of your {% data variables.product.prodname_ghe_server %} license
 - The customer name on your {% data variables.product.prodname_ghe_server %} license
 - The version of {% data variables.product.product_location_enterprise %}{% endif %}
-- The hostname of your {% data variables.product.product_name %} instance
+- The hostname of {% data variables.product.product_location %}
 - The organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that's connected to {% data variables.product.product_location %}
 - The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_dotcom_the_website %}
+- If Transport Layer Security (TLS) is enabled and configured on {% data variables.product.product_location %}{% ifversion ghes %}
+- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.product.product_location %}, and the date and time of enablement{% endif %}
+
+{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
 
 Enabling {% data variables.product.prodname_github_connect %} also creates a {% data variables.product.prodname_github_app %} owned by your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_dotcom_the_website %}.
 {% ifversion ghes %}

content/admin/enterprise-management/configuring-clustering/about-clustering.md

@@ -4,7 +4,7 @@ intro: '{% data variables.product.prodname_ghe_server %} clustering allows servi
 redirect_from:
   - /enterprise/admin/clustering/overview
   - /enterprise/admin/clustering/about-clustering
-  - /enterprise/admin/clustering/clustering-overview/
+  - /enterprise/admin/clustering/clustering-overview
   - /enterprise/admin/enterprise-management/about-clustering
   - /admin/enterprise-management/about-clustering
 versions:

content/admin/enterprise-management/configuring-clustering/index.md

@@ -4,7 +4,7 @@ intro: Learn about clustering and differences with high availability.
 redirect_from:
   - /enterprise/admin/clustering/setting-up-the-cluster-instances
   - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
-  - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/
+  - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster
   - /enterprise/admin/enterprise-management/configuring-clustering
 versions:
   ghes: '*'

content/admin/enterprise-management/configuring-high-availability/index.md

@@ -2,9 +2,9 @@
 title: Configuring high availability
 redirect_from:
   - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
-  - /enterprise/admin/guides/installation/high-availability-cluster-configuration/
-  - /enterprise/admin/guides/installation/high-availability-configuration/
-  - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/
+  - /enterprise/admin/guides/installation/high-availability-cluster-configuration
+  - /enterprise/admin/guides/installation/high-availability-configuration
+  - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
   - /enterprise/admin/enterprise-management/configuring-high-availability
 intro: '{% data variables.product.prodname_ghe_server %} supports a high availability mode of operation designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary appliance.'
 versions:

content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md

@@ -3,7 +3,7 @@ title: Configuring collectd
 intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.'
 redirect_from:
   - /enterprise/admin/installation/configuring-collectd
-  - /enterprise/admin/articles/configuring-collectd/
+  - /enterprise/admin/articles/configuring-collectd
   - /enterprise/admin/enterprise-management/configuring-collectd
   - /admin/enterprise-management/configuring-collectd
 versions:

content/admin/enterprise-management/monitoring-your-appliance/index.md

@@ -2,8 +2,8 @@
 title: Monitoring your appliance
 intro: 'As use of {% data variables.product.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.'
 redirect_from:
-  - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting/
-  - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/
+  - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
+  - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
   - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance
   - /enterprise/admin/enterprise-management/monitoring-your-appliance
 versions:

content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md

@@ -3,7 +3,7 @@ title: Monitoring using SNMP
 intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.'
 redirect_from:
   - /enterprise/admin/installation/monitoring-using-snmp
-  - /enterprise/admin/articles/monitoring-using-snmp/
+  - /enterprise/admin/articles/monitoring-using-snmp
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
   - /admin/enterprise-management/monitoring-using-snmp
 versions:

content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md

@@ -2,7 +2,7 @@
 title: Recommended alert thresholds
 intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.'
 redirect_from:
-  - /enterprise/admin/guides/installation/about-recommended-alert-thresholds/
+  - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/recommended-alert-thresholds
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds

content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md

@@ -2,8 +2,8 @@
 title: Updating the virtual machine and physical resources
 intro: 'Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.'
 redirect_from:
-  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm/'
-  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/'
+  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm'
+  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources'
   - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources
   - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources
 versions: