diff --git a/.devcontainer/Dockerfile b/.devcontainer/Dockerfile
index c37a7152ec..89633bf993 100644
--- a/.devcontainer/Dockerfile
+++ b/.devcontainer/Dockerfile
@@ -14,3 +14,8 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 
 # [Optional] Uncomment if you want to install more global node modules
 # RUN su node -c "npm install -g <your-package-list-here>"
+
+# Install the GitHub CLI see:
+# https://github.com/microsoft/vscode-dev-containers/blob/3d59f9fe37edb68f78874620f33dac5a62ef2b93/script-library/docs/github.md
+COPY library-scripts/github-debian.sh /tmp/library-scripts/
+RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index a10ad565e4..d19f215e62 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -20,7 +20,6 @@
 		"sissel.shopify-liquid",
 		"davidanson.vscode-markdownlint",
 		"bierner.markdown-preview-github-styles",
-		"yzhang.markdown-all-in-one",
 		"streetsidesoftware.code-spell-checker",
 		"hubwriter.open-reusable"
 	],
diff --git a/.devcontainer/library-scripts/github-debian.sh b/.devcontainer/library-scripts/github-debian.sh
new file mode 100644
index 0000000000..2d474fdefa
--- /dev/null
+++ b/.devcontainer/library-scripts/github-debian.sh
@@ -0,0 +1,43 @@
+#!/usr/bin/env bash
+#-------------------------------------------------------------------------------------------------------------
+# Copyright (c) Microsoft Corporation. All rights reserved.
+# Licensed under the MIT License. See https://go.microsoft.com/fwlink/?linkid=2090316 for license information.
+#-------------------------------------------------------------------------------------------------------------
+#
+# Docs: https://github.com/microsoft/vscode-dev-containers/blob/master/script-library/docs/github.md
+#
+# Syntax: ./github-debian.sh [version]
+
+CLI_VERSION=${1:-"latest"}
+
+set -e
+
+if [ "$(id -u)" -ne 0 ]; then
+    echo -e 'Script must be run as root. Use sudo, su, or add "USER root" to your Dockerfile before running this script.'
+    exit 1
+fi
+
+export DEBIAN_FRONTEND=noninteractive
+
+# Install curl, apt-transport-https or gpg if missing
+if ! dpkg -s curl ca-certificates > /dev/null 2>&1; then
+    if [ ! -d "/var/lib/apt/lists" ] || [ "$(ls /var/lib/apt/lists/ | wc -l)" = "0" ]; then
+        apt-get update
+    fi
+    apt-get -y install --no-install-recommends curl ca-certificates
+fi
+
+# Get latest release number if latest is specified
+if [ "${CLI_VERSION}" = "latest" ] ||  [ "${CLI_VERSION}" = "current" ] ||  [ "${CLI_VERSION}" = "lts" ]; then
+    LATEST_RELEASE=$(curl -sSL -H "Accept: application/vnd.github.v3+json" "https://api.github.com/repos/cli/cli/releases?per_page=1&page=1")
+    CLI_VERSION=$(echo ${LATEST_RELEASE} | grep -oE 'tag_name":\s*"v[^"]+' | sed -n '/tag_name":\s*"v/s///p')
+fi
+
+# Install the GitHub CLI
+echo "Downloading github CLI..."
+curl -OsSL https://github.com/cli/cli/releases/download/v${CLI_VERSION}/gh_${CLI_VERSION}_linux_amd64.deb
+echo "Installing github CLI..."
+apt-get install ./gh_${CLI_VERSION}_linux_amd64.deb
+echo "Removing github CLI deb file after installation..."
+rm -rf ./gh_${CLI_VERSION}_linux_amd64.deb
+echo "Done!"
diff --git a/.github/actions-scripts/content-changes-table-comment.js b/.github/actions-scripts/content-changes-table-comment.js
index c0cb0ce176..91a62cb95f 100755
--- a/.github/actions-scripts/content-changes-table-comment.js
+++ b/.github/actions-scripts/content-changes-table-comment.js
@@ -1,23 +1,20 @@
 #!/usr/bin/env node
 
-import createStagingAppName from '../../script/deployment/create-staging-app-name.js'
 import * as github from '@actions/github'
 import { setOutput } from '@actions/core'
 
+const { GITHUB_TOKEN, APP_URL } = process.env
 const context = github.context
 
-const githubToken = process.env.GITHUB_TOKEN
-if (!githubToken) {
+if (!GITHUB_TOKEN) {
   throw new Error(`GITHUB_TOKEN environment variable not set`)
 }
 
-const stagingPrefix = createStagingAppName({
-  repo: context.payload.repository.name,
-  pullNumber: context.payload.number,
-  branch: context.payload.pull_request.head.ref,
-})
+if (!APP_URL) {
+  throw new Error(`APP_URL environment variable not set`)
+}
 
-const octokit = github.getOctokit(githubToken)
+const octokit = github.getOctokit(GITHUB_TOKEN)
 
 const response = await octokit.rest.repos.compareCommits({
   owner: context.repo.owner,
@@ -29,7 +26,7 @@ const response = await octokit.rest.repos.compareCommits({
 const { files } = response.data
 
 let markdownTable =
-  '| **Source** | **Staging** | **Production** | **What Changed** |\n|:----------- |:----------- |:----------- |:----------- |\n'
+  '| **Source** | **Preview** | **Production** | **What Changed** |\n|:----------- |:----------- |:----------- |:----------- |\n'
 
 const pathPrefix = 'content/'
 const articleFiles = files.filter(
@@ -39,14 +36,14 @@ for (const file of articleFiles) {
   const sourceUrl = file.blob_url
   const fileName = file.filename.slice(pathPrefix.length)
   const fileUrl = fileName.slice(0, fileName.lastIndexOf('.'))
-  const stagingLink = `https://${stagingPrefix}.herokuapp.com/${fileUrl}`
+  const previewLink = `https://${APP_URL}/${fileUrl}`
   const productionLink = `https://docs.github.com/${fileUrl}`
   let markdownLine = ''
 
   if (file.status === 'modified') {
-    markdownLine = `| [content/${fileName}](${sourceUrl}) | [Modified](${stagingLink}) | [Original](${productionLink}) | |\n`
+    markdownLine = `| [content/${fileName}](${sourceUrl}) | [Modified](${previewLink}) | [Original](${productionLink}) | |\n`
   } else if (file.status === 'added') {
-    markdownLine = `| New file: [content/${fileName}](${sourceUrl}) | [Modified](${stagingLink}) | | |\n`
+    markdownLine = `| New file: [content/${fileName}](${sourceUrl}) | [Modified](${previewLink}) | | |\n`
   }
   markdownTable += markdownLine
 }
diff --git a/.github/actions-scripts/get-preview-app-info.sh b/.github/actions-scripts/get-preview-app-info.sh
new file mode 100755
index 0000000000..e7f9f87366
--- /dev/null
+++ b/.github/actions-scripts/get-preview-app-info.sh
@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+
+# [start-readme]
+#
+# This script sets environment variables with info about the preview app for a given PR
+#
+# [end-readme]
+
+# ENV VARS NEEDED TO RUN
+[[ -z $GITHUB_REPOSITORY ]] && { echo "Missing GITHUB_REPOSITORY. Exiting."; exit 1; }
+[[ -z $PR_NUMBER ]] && { echo "Missing PR_NUMBER. Exiting."; exit 1; }
+[[ -z $GITHUB_ENV ]] && { echo "Missing GITHUB_ENV. Exiting."; exit 1; }
+
+# Number of resource groups that we use to split preview envs across
+PREVIEW_ENV_RESOURCE_GROUPS=4
+
+REPO_NAME="${GITHUB_REPOSITORY#*\/}"
+echo "REPO_NAME=${REPO_NAME}" >> $GITHUB_ENV
+
+DEPLOYMENT_NAME="${REPO_NAME}-pr-${PR_NUMBER}"
+echo "DEPLOYMENT_NAME=${DEPLOYMENT_NAME}" >> $GITHUB_ENV
+
+RESOURCE_GROUP="preview-env-${REPO_NAME}-$((${PR_NUMBER} % ${PREVIEW_ENV_RESOURCE_GROUPS}))"
+echo "RESOURCE_GROUP=${RESOURCE_GROUP}" >> $GITHUB_ENV
+
+APP_NAME_SHORT="${REPO_NAME}-preview-${PR_NUMBER}"
+echo "APP_NAME_SHORT=${APP_NAME_SHORT}" >> $GITHUB_ENV
+
+IMAGE_REPO="${GITHUB_REPOSITORY}/pr-${PR_NUMBER}"
+echo "IMAGE_REPO=${IMAGE_REPO}" >> $GITHUB_ENV
+
+# Since this incurs a network request and can be slow, we make it optional
+if [ $FULL_APP_INFO ]; then
+  APP_INFO=$(az webapp list -g ${RESOURCE_GROUP} --query "[?tags.DocsAppName == '${APP_NAME_SHORT}'].{defaultHostName:defaultHostName, name:name} | [0]")
+
+  APP_URL=$(echo $APP_INFO | jq '.defaultHostName' | tr -d '"')
+  echo "APP_URL=${APP_URL}" >> $GITHUB_ENV
+
+  APP_NAME_FULL=$(echo $APP_INFO | jq '.name' | tr -d '"')
+  echo "APP_NAME_FULL=${APP_NAME_FULL}" >> $GITHUB_ENV
+fi
diff --git a/.github/workflows/azure-preview-env-deploy.yml b/.github/workflows/azure-preview-env-deploy.yml
index f8233025ee..2a54474359 100644
--- a/.github/workflows/azure-preview-env-deploy.yml
+++ b/.github/workflows/azure-preview-env-deploy.yml
@@ -1,4 +1,4 @@
-name: Deploy Azure Preview Environment
+name: Azure - Deploy Preview Environment
 
 # **What it does**: Build and deploy to an Azure preview environment
 # **Why we have it**: It's our preview environment deploy mechanism, only applicable to docs-internal
@@ -17,6 +17,11 @@ on:
   # request creator has permission to access secrets.
   pull_request:
   workflow_dispatch:
+    inputs:
+      PR_NUMBER:
+        description: 'PR Number'
+        type: string
+        required: true
 
 permissions:
   contents: read
@@ -30,31 +35,19 @@ concurrency:
 jobs:
   build-and-deploy-azure-preview:
     if: ${{ github.repository == 'github/docs-internal' }}
-    name: Build and deploy image to Azure
+    name: Build and deploy Azure preview environment
     runs-on: ubuntu-latest
     timeout-minutes: 15
     environment:
       name: preview-env-${{ github.event.number }}
       url: ${{ steps.deploy.outputs.defaultHostName }}
     env:
-      GITHUB_EVENT_NUMBER: ${{ github.event.number }}
-      PREVIEW_ENV_RESOURCE_GROUPS: 4
+      PR_NUMBER: ${{ github.event.number || github.event.inputs.PR_NUMBER }}
       NONPROD_REGISTRY_USERNAME: ghdocs
       APP_LOCATION: eastus
       ENABLE_EARLY_ACCESS: ${{ github.repository == 'github/docs-internal' }}
-      # Image tag is unique to each workflow run so that it always triggers a new deployment
-      DOCKER_IMAGE: ${{ secrets.NONPROD_REGISTRY_SERVER }}/${{ github.repository }}/pr-${{ github.event.number }}:${{ github.event.pull_request.head.sha }}-${{ github.run_number }}-${{ github.run_attempt }}
 
     steps:
-      - name: 'Set env vars'
-        id: vars
-        run: |
-          REPO_NAME=${GITHUB_REPOSITORY#*\/}
-          echo "REPO_NAME=${REPO_NAME}" >> $GITHUB_ENV
-          echo "DEPLOYMENT_NAME=${REPO_NAME}-pr-${GITHUB_EVENT_NUMBER}" >> $GITHUB_ENV
-          echo "RESOURCE_GROUP=preview-env-${REPO_NAME}-$((${GITHUB_EVENT_NUMBER} % ${PREVIEW_ENV_RESOURCE_GROUPS}))" >> $GITHUB_ENV
-          echo "APP_NAME=${REPO_NAME}-preview-${GITHUB_EVENT_NUMBER}" >> $GITHUB_ENV
-
       - name: 'Az CLI login'
         uses: azure/login@1f63701bf3e6892515f1b7ce2d2bf1708b46beaf
         with:
@@ -81,6 +74,14 @@ jobs:
       - name: Check out LFS objects
         run: git lfs checkout
 
+      - name: Get preview app info
+        run: .github/actions-scripts/get-preview-app-info.sh
+
+      - name: 'Set env vars'
+        run: |
+          # Image tag is unique to each workflow run so that it always triggers a new deployment
+          echo "DOCKER_IMAGE=${{ secrets.NONPROD_REGISTRY_SERVER }}/${IMAGE_REPO}:${{ github.event.pull_request.head.sha }}-${{ github.run_number }}-${{ github.run_attempt }}" >> $GITHUB_ENV
+
       - if: ${{ env.ENABLE_EARLY_ACCESS }}
         name: Determine which docs-early-access branch to clone
         id: 'check-early-access'
@@ -155,7 +156,7 @@ jobs:
           subscriptionId: ${{ secrets.NONPROD_SUBSCRIPTION_ID }}
           template: ./azure-preview-env-template.json
           deploymentName: ${{ env.DEPLOYMENT_NAME }}
-          parameters: appName="${{ env.APP_NAME }}"
+          parameters: appName="${{ env.APP_NAME_SHORT }}"
             location="${{ env.APP_LOCATION }}"
             linuxFxVersion="DOCKER|${{ env.DOCKER_IMAGE }}"
             dockerRegistryUrl="https://${{ secrets.NONPROD_REGISTRY_SERVER }}"
diff --git a/.github/workflows/azure-preview-env-destroy.yml b/.github/workflows/azure-preview-env-destroy.yml
index 8f41651998..d9fe2c5a5a 100644
--- a/.github/workflows/azure-preview-env-destroy.yml
+++ b/.github/workflows/azure-preview-env-destroy.yml
@@ -1,4 +1,4 @@
-name: Destroy Azure Preview Env
+name: Azure - Destroy Preview Env
 
 # **What it does**: Destroys resources associated with a PRs Azure preview environment
 # **Why we have it**: Closed PRs don't need apps
@@ -9,49 +9,47 @@ on:
     types:
       - closed
       - locked
+  workflow_dispatch:
+    inputs:
+      PR_NUMBER:
+        description: 'PR Number'
+        type: string
+        required: true
 
 jobs:
   destory-azure-preview-env:
     name: Destroy
+    if: ${{ github.repository == 'github/docs-internal' }}
     runs-on: ubuntu-latest
     timeout-minutes: 5
     env:
-      GITHUB_EVENT_NUMBER: ${{ github.event.number }}
-      PREVIEW_ENV_RESOURCE_GROUPS: 4
+      PR_NUMBER: ${{ github.event.number || github.event.inputs.PR_NUMBER }}
       NONPROD_REGISTRY_NAME: ghdocs
-      IMAGE_REPO: ${{ github.repository }}/pr-${{ github.event.number }}
 
     steps:
-      - name: 'Set env vars'
-        id: vars
-        run: |
-          REPO_NAME=${GITHUB_REPOSITORY#*\/}
-          echo "RESOURCE_GROUP=preview-env-${REPO_NAME}-$((${GITHUB_EVENT_NUMBER} % ${PREVIEW_ENV_RESOURCE_GROUPS}))" >> $GITHUB_ENV
-          echo "DEPLOYMENT_NAME=${REPO_NAME}-pr-${GITHUB_EVENT_NUMBER}" >> $GITHUB_ENV
-          echo "APP_NAME=${REPO_NAME}-preview-${GITHUB_EVENT_NUMBER}" >> $GITHUB_ENV
-
       - name: 'Az CLI login'
         uses: azure/login@1f63701bf3e6892515f1b7ce2d2bf1708b46beaf
         with:
           creds: ${{ secrets.NONPROD_AZURE_CREDENTIALS }}
 
+      - name: Check out repo
+        uses: actions/checkout@1e204e9a9253d643386038d443f96446fa156a97
+
+      - name: Get preview app info
+        env:
+          FULL_APP_INFO: 1
+        run: .github/actions-scripts/get-preview-app-info.sh
+
       # Succeed despite any non-zero exit code (e.g. if there is no deployment to cancel)
       - name: 'Cancel any in progress deployments'
         run: |
           az deployment group cancel --name ${{ env.DEPLOYMENT_NAME }} -g ${{ env.RESOURCE_GROUP }} || true
 
-      # The full app name is obfuscated by an identifier, so we need to query to find the one for this PR
-      - name: 'Get full app name'
-        id: full-app-name
-        run: |
-          FULL_APP_NAME=$(az webapp list -g ${{ env.RESOURCE_GROUP }} --query "[?tags.DocsAppName == '${{ env.APP_NAME }}'})].name | [0]")
-          echo "::set-output name=result::${FULL_APP_NAME}"
-
       # Delete web app (which will also delete the App Service plan)
       # This will succeed even if the app doesn't exist / has already been deleted
       - name: 'Delete App Service App (which will also delete the App Service plan)'
         run: |
-          az webapp delete -n ${{ steps.full-app-name.result }} -g ${{ env.RESOURCE_GROUP }})
+          az webapp delete -n ${{ env.APP_NAME_FULL }} -g ${{ env.RESOURCE_GROUP }}
 
       # Untag all images under this PR's container registry repo - the container registry will automatically remove untagged images.
       # This will fail if the IMAGE_REPO doesn't exist, but we don't care
@@ -63,4 +61,4 @@ jobs:
       - uses: strumwolf/delete-deployment-environment@45c821e46baa405e25410700fe2e9643929706a0
         with:
           token: ${{ secrets.DOCUBOT_REPO_PAT }}
-          environment: preview-env-${{ github.event.number }}
+          environment: preview-env-${{ env.PR_NUMBER }}
diff --git a/.github/workflows/codespaces-prebuild.yml b/.github/workflows/codespaces-prebuild.yml
deleted file mode 100644
index 1a31b163ca..0000000000
--- a/.github/workflows/codespaces-prebuild.yml
+++ /dev/null
@@ -1,30 +0,0 @@
-name: Prebuild Codespaces
-
-# **What it does**: Prebuild the Codespaces image using powerful machines.
-#   See https://github.com/github/codespaces-precache#readme for more details.
-#   IMPORTANT: Requires we set a `EXPERIMENTAL_CODESPACE_CACHE_TOKEN` Codespaces
-#   Secret (NOT an Actions Secret) in the repository.
-# **Why we have it**: Reduces startup time when booting Codespaces.
-# **Who does it impact**: Any Docs contributors who want to use Codespaces.
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-# Currently requires write, but in the future will only require read
-permissions:
-  contents: write
-
-jobs:
-  createPrebuild:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-      - uses: github/codespaces-precache@2ad40630d7e3e45e8725d6a74656cb6dd17363dc
-        with:
-          regions: WestUs2 EastUs WestEurope SouthEastAsia
-          sku_name: basicLinux32gb
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/content-changes-table-comment.yml b/.github/workflows/content-changes-table-comment.yml
index 5eece574db..8b9127dec9 100644
--- a/.github/workflows/content-changes-table-comment.yml
+++ b/.github/workflows/content-changes-table-comment.yml
@@ -45,10 +45,22 @@ jobs:
     needs: PR-Preview-Links
     if: ${{ needs.PR-Preview-Links.outputs.filterContentDir == 'true' }}
     runs-on: ubuntu-latest
+    env:
+      PR_NUMBER: ${{ github.event.pull_request.number }}
     steps:
+      - name: 'Az CLI login'
+        uses: azure/login@1f63701bf3e6892515f1b7ce2d2bf1708b46beaf
+        with:
+          creds: ${{ secrets.NONPROD_AZURE_CREDENTIALS }}
+
       - name: check out repo content
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
+      - name: Get preview app info
+        env:
+          FULL_APP_INFO: 1
+        run: .github/actions-scripts/get-preview-app-info.sh
+
       - name: Setup Node
         uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
@@ -57,12 +69,13 @@ jobs:
 
       - name: Install temporary dependencies
         run: |
-          npm install --no-save github-slugger
+          npm install --no-save github-slugger --registry https://registry.npmjs.org/
 
       - name: Get changes table
         id: changes
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          APP_URL: ${{ env.APP_URL }}
         run: .github/actions-scripts/content-changes-table-comment.js
 
       - name: Find content directory changes comment
diff --git a/.github/workflows/optimize-images.yml b/.github/workflows/optimize-images.yml
index db5ea1b363..9abe9bb34b 100644
--- a/.github/workflows/optimize-images.yml
+++ b/.github/workflows/optimize-images.yml
@@ -50,6 +50,6 @@ jobs:
           git push --set-upstream origin $BRANCH
 
           echo "Open a pull request"
-          gh pr create --title "Optimize images" --body "Optimize images"
+          gh pr create --title "Optimize images" --body "Optimize images" --reviewer "@github/docs-engineering"
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 1678bffc37..87a8347b79 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -47,9 +47,13 @@ jobs:
       - name: Check out repo
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
         with:
+          lfs: true
           # Enables cloning the Early Access repo later with the relevant PAT
           persist-credentials: 'false'
 
+      - name: Checkout LFS objects
+        run: git lfs checkout
+
       - name: Gather files changed
         uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
         id: get_diff_files
diff --git a/.github/workflows/workflow-lint.yml b/.github/workflows/workflow-lint.yml
deleted file mode 100644
index 698aa0f733..0000000000
--- a/.github/workflows/workflow-lint.yml
+++ /dev/null
@@ -1,33 +0,0 @@
-name: Lint workflows
-
-# **What it does**: This lints our workflow files.
-# **Why we have it**: We want some level of consistency in our workflow files.
-# **Who does it impact**: Docs engineering.
-
-on:
-  workflow_dispatch:
-  pull_request:
-    paths:
-      - '.github/workflows/*.yml'
-      - '.github/workflows/*.yaml'
-
-permissions:
-  contents: read
-
-# This allows a subsequently queued workflow run to interrupt previous runs
-concurrency:
-  group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  lint:
-    if: ${{ github.repository == 'github/docs-internal' }}
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out repo
-        uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
-
-      - name: Run linter
-        uses: cschleiden/actions-linter@caffd707beda4fc6083926a3dff48444bc7c24aa
-        with:
-          workflows: '[".github/workflows/*.yml", ".github/workflows/*.yaml", "!.github/workflows/remove-from-fr-board.yaml", "!.github/workflows/staging-deploy-pr.yml", "!.github/workflows/triage-issue-comments.yml", "!.github/workflows/azure-preview-env-deploy.yml", "!.github/workflows/azure-preview-env-destroy.yml"]'
diff --git a/Dockerfile b/Dockerfile
index 88e861a470..912301bc55 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -76,9 +76,6 @@ ENV NODE_ENV production
 # Whether to hide iframes, add warnings to external links
 ENV AIRGAP false
 
-# By default we typically don't want to run in clustered mode
-ENV WEB_CONCURRENCY 1
-
 # Preferred port for server.mjs
 ENV PORT 4000
 
diff --git a/assets/images/help/2fa/2fa-recovery-code-link.png b/assets/images/help/2fa/2fa-recovery-code-link.png
index 588f9f6366..02b7bfe6fe 100644
Binary files a/assets/images/help/2fa/2fa-recovery-code-link.png and b/assets/images/help/2fa/2fa-recovery-code-link.png differ
diff --git a/assets/images/help/2fa/2fa-type-verify-recovery-code.png b/assets/images/help/2fa/2fa-type-verify-recovery-code.png
index 439c25b18a..862e7ffa15 100644
Binary files a/assets/images/help/2fa/2fa-type-verify-recovery-code.png and b/assets/images/help/2fa/2fa-type-verify-recovery-code.png differ
diff --git a/assets/images/help/2fa/alt-verifications.png b/assets/images/help/2fa/alt-verifications.png
index 8fb229d2c1..be89b92267 100644
Binary files a/assets/images/help/2fa/alt-verifications.png and b/assets/images/help/2fa/alt-verifications.png differ
diff --git a/assets/images/help/2fa/no-access-link.png b/assets/images/help/2fa/no-access-link.png
index 9bbd79b34d..efe6927522 100644
Binary files a/assets/images/help/2fa/no-access-link.png and b/assets/images/help/2fa/no-access-link.png differ
diff --git a/assets/images/help/2fa/one-time-password-field.png b/assets/images/help/2fa/one-time-password-field.png
index 3d8719d6f1..3944f19f1e 100644
Binary files a/assets/images/help/2fa/one-time-password-field.png and b/assets/images/help/2fa/one-time-password-field.png differ
diff --git a/assets/images/help/2fa/reset-auth-settings.png b/assets/images/help/2fa/reset-auth-settings.png
index 2c07ea0338..c1c3d78abf 100644
Binary files a/assets/images/help/2fa/reset-auth-settings.png and b/assets/images/help/2fa/reset-auth-settings.png differ
diff --git a/assets/images/help/2fa/send-one-time-password.png b/assets/images/help/2fa/send-one-time-password.png
index a14cacaa56..56c1b3fd6b 100644
Binary files a/assets/images/help/2fa/send-one-time-password.png and b/assets/images/help/2fa/send-one-time-password.png differ
diff --git a/assets/images/help/2fa/try-recovering-your-account-link.png b/assets/images/help/2fa/try-recovering-your-account-link.png
new file mode 100644
index 0000000000..8744a58e2e
Binary files /dev/null and b/assets/images/help/2fa/try-recovering-your-account-link.png differ
diff --git a/assets/images/help/2fa/verify-email-address.png b/assets/images/help/2fa/verify-email-address.png
new file mode 100644
index 0000000000..83615a8163
Binary files /dev/null and b/assets/images/help/2fa/verify-email-address.png differ
diff --git a/assets/images/help/organizations/member-privileges.png b/assets/images/help/organizations/member-privileges.png
new file mode 100644
index 0000000000..73a64a0f32
Binary files /dev/null and b/assets/images/help/organizations/member-privileges.png differ
diff --git a/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png b/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png
index 105b742e27..8a542eb9ed 100644
Binary files a/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png and b/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png differ
diff --git a/assets/images/help/repository/code-scanning-alert.png b/assets/images/help/repository/code-scanning-alert.png
index 304db06484..0c83de9e3e 100644
Binary files a/assets/images/help/repository/code-scanning-alert.png and b/assets/images/help/repository/code-scanning-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-create-issue-for-alert.png b/assets/images/help/repository/code-scanning-create-issue-for-alert.png
index 5b9d0d719a..2237940b46 100644
Binary files a/assets/images/help/repository/code-scanning-create-issue-for-alert.png and b/assets/images/help/repository/code-scanning-create-issue-for-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-experimental-alert-show.png b/assets/images/help/repository/code-scanning-experimental-alert-show.png
index eb7b169ade..00e3fb3992 100644
Binary files a/assets/images/help/repository/code-scanning-experimental-alert-show.png and b/assets/images/help/repository/code-scanning-experimental-alert-show.png differ
diff --git a/assets/images/help/repository/code-scanning-free-text-search-areas.png b/assets/images/help/repository/code-scanning-free-text-search-areas.png
index 3bfcef8316..541a7702a5 100644
Binary files a/assets/images/help/repository/code-scanning-free-text-search-areas.png and b/assets/images/help/repository/code-scanning-free-text-search-areas.png differ
diff --git a/assets/images/help/repository/code-scanning-pr-alert.png b/assets/images/help/repository/code-scanning-pr-alert.png
index f197d6c28a..35070b7151 100644
Binary files a/assets/images/help/repository/code-scanning-pr-alert.png and b/assets/images/help/repository/code-scanning-pr-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-show-paths.png b/assets/images/help/repository/code-scanning-show-paths.png
index 64a5e2e4c5..16430c56dd 100644
Binary files a/assets/images/help/repository/code-scanning-show-paths.png and b/assets/images/help/repository/code-scanning-show-paths.png differ
diff --git a/assets/images/help/settings/accessibility-tab.png b/assets/images/help/settings/accessibility-tab.png
deleted file mode 100644
index 0228cb51c4..0000000000
Binary files a/assets/images/help/settings/accessibility-tab.png and /dev/null differ
diff --git a/assets/images/help/settings/codespaces-tab.png b/assets/images/help/settings/codespaces-tab.png
deleted file mode 100644
index 2372d49ca2..0000000000
Binary files a/assets/images/help/settings/codespaces-tab.png and /dev/null differ
diff --git a/assets/images/help/settings/org-settings-pages.png b/assets/images/help/settings/org-settings-pages.png
deleted file mode 100644
index a917c59786..0000000000
Binary files a/assets/images/help/settings/org-settings-pages.png and /dev/null differ
diff --git a/assets/images/help/settings/settings-sidebar-billing-plans.png b/assets/images/help/settings/settings-sidebar-billing-plans.png
deleted file mode 100644
index dfb55ba550..0000000000
Binary files a/assets/images/help/settings/settings-sidebar-billing-plans.png and /dev/null differ
diff --git a/assets/images/help/settings/settings-sidebar-blocked-users.png b/assets/images/help/settings/settings-sidebar-blocked-users.png
deleted file mode 100644
index 73664a4ced..0000000000
Binary files a/assets/images/help/settings/settings-sidebar-blocked-users.png and /dev/null differ
diff --git a/assets/images/help/settings/settings-sidebar-interaction-limits.png b/assets/images/help/settings/settings-sidebar-interaction-limits.png
deleted file mode 100644
index 4d0518780e..0000000000
Binary files a/assets/images/help/settings/settings-sidebar-interaction-limits.png and /dev/null differ
diff --git a/assets/images/help/settings/settings-sidebar-organizations.png b/assets/images/help/settings/settings-sidebar-organizations.png
deleted file mode 100644
index ed5745b50e..0000000000
Binary files a/assets/images/help/settings/settings-sidebar-organizations.png and /dev/null differ
diff --git a/assets/images/help/settings/settings-sidebar-third-party-access.png b/assets/images/help/settings/settings-sidebar-third-party-access.png
deleted file mode 100644
index d1fbb9d5f3..0000000000
Binary files a/assets/images/help/settings/settings-sidebar-third-party-access.png and /dev/null differ
diff --git a/assets/images/help/settings/user-settings-pages.png b/assets/images/help/settings/user-settings-pages.png
deleted file mode 100644
index ac7518a720..0000000000
Binary files a/assets/images/help/settings/user-settings-pages.png and /dev/null differ
diff --git a/azure-preview-env-template.json b/azure-preview-env-template.json
index 32dbd849fa..911a103d15 100644
--- a/azure-preview-env-template.json
+++ b/azure-preview-env-template.json
@@ -83,10 +83,6 @@
                           "name": "DEPLOYMENT_ENV",
                           "value": "azure"
                       },
-                      {
-                          "name": "WEB_CONCURRENCY",
-                          "value": "1"
-                      },
                       {
                           "name": "ENABLED_LANGUAGES",
                           "value": "en"
diff --git a/components/article/PlatformPicker.tsx b/components/article/PlatformPicker.tsx
index d4d8c52ccf..861a7b11d0 100644
--- a/components/article/PlatformPicker.tsx
+++ b/components/article/PlatformPicker.tsx
@@ -2,6 +2,7 @@ import { useEffect, useState } from 'react'
 import Cookies from 'js-cookie'
 import { SubNav, TabNav, UnderlineNav } from '@primer/components'
 import { sendEvent, EventType } from 'components/lib/events'
+import { useRouter } from 'next/router'
 
 import { useArticleContext } from 'components/context/ArticleContext'
 import parseUserAgent from 'components/lib/user-agent'
@@ -50,6 +51,7 @@ type Props = {
 export const PlatformPicker = ({ variant = 'subnav' }: Props) => {
   const { defaultPlatform, detectedPlatforms } = useArticleContext()
   const [currentPlatform, setCurrentPlatform] = useState(defaultPlatform || '')
+  const { asPath } = useRouter()
 
   // Run on mount for client-side only features
   useEffect(() => {
@@ -63,7 +65,7 @@ export const PlatformPicker = ({ variant = 'subnav' }: Props) => {
 
     // always trigger this on initial render. if the default doesn't change the other useEffect won't fire
     showPlatformSpecificContent(platform)
-  }, [])
+  }, [asPath])
 
   // Make sure we've always selected a platform that exists in the article
   useEffect(() => {
diff --git a/components/page-header/VersionPicker.tsx b/components/page-header/VersionPicker.tsx
index a6fbe81b64..cd7623b783 100644
--- a/components/page-header/VersionPicker.tsx
+++ b/components/page-header/VersionPicker.tsx
@@ -26,8 +26,8 @@ export const VersionPicker = ({ variant }: Props) => {
     selected: allVersions[currentVersion].versionTitle === permalink.pageVersionTitle,
     item: <Link href={permalink.href}>{permalink.pageVersionTitle}</Link>,
   }))
-  const hasEnterpriseVersions = (page.permalinks || []).find((permalink) =>
-    permalink.pageVersion.startsWith('enterprise-version')
+  const hasEnterpriseVersions = (page.permalinks || []).some((permalink) =>
+    permalink.pageVersion.startsWith('enterprise-server')
   )
 
   if (hasEnterpriseVersions) {
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 5c930d7817..6b8b438787 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
-product: '{% ifversion fpt %}{% data reusables.gated-features.user-repo-collaborators %}{% endif %}'
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0546453704..d0aef51457 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -9,7 +9,6 @@ redirect_from:
   - /articles/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
-product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -21,8 +20,12 @@ topics:
 shortTitle: Remove yourself
 ---
 {% data reusables.user_settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 2. In the left sidebar, click **Repositories**.
   ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
 3. Next to the repository you want to leave, click **Leave**.
   ![Leave button](/assets/images/help/repository/repo-leave.png)
 4. Read the warning carefully, then click "I understand, leave this repository."
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
index ef23b4e09b..1b8e92ef1e 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -12,13 +12,12 @@ shortTitle: Integrate Jira with projects
 ---
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
-3. In the left sidebar, click **{% data variables.product.prodname_oauth_apps %}**.
-![{% data variables.product.prodname_oauth_apps %} tab in the left sidebar](/assets/images/help/settings/developer-settings-oauth-apps.png)
-3. Click **Register a new application**.
-4. Under **Application name**, type "Jira".
-5. Under **Homepage URL**, type the full URL to your Jira instance.
-6. Under **Authorization callback URL**, type the full URL to your Jira instance.
-7. Click **Register application**.
+{% data reusables.user-settings.oauth_apps %}
+1. Click **Register a new application**.
+2. Under **Application name**, type "Jira".
+3. Under **Homepage URL**, type the full URL to your Jira instance.
+4. Under **Authorization callback URL**, type the full URL to your Jira instance.
+5. Click **Register application**.
 ![Register application button](/assets/images/help/oauth/register-application-button.png)
 8. Under **Developer applications**, note the "Client ID" and "Client Secret" values.
 ![Client ID and Client Secret](/assets/images/help/oauth/client-id-and-secret.png)
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index f57df57ad7..a4c3ff7d6e 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,7 +14,6 @@ shortTitle: Managing your tab size
 If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings.
 
 {% data reusables.user_settings.access_settings %}
-1. In the user settings sidebar, click **Appearance**.
-   !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 2. Under "Tab size preference", select the drop-down menu and choose your preference.
    ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png )
diff --git a/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 95e05bb95c..2910096e3c 100644
--- a/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -218,6 +218,10 @@ For example:
 curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
 ```
 
+### Adding permissions settings
+
+{% data reusables.actions.oidc-permissions-token %}
+
 ## Updating your workflows for OIDC
 
 You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
diff --git a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index c3835e7b73..e1c0cdcf16 100644
--- a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -56,14 +56,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 80231b121a..5f599d3228 100644
--- a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -50,14 +50,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index 4d8d1b37fa..ba2b53c596 100644
--- a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -37,14 +37,7 @@ If your cloud provider doesn't yet offer an official action, you can update your
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Using official actions
 
diff --git a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index ec07382cbc..32f5731ea7 100644
--- a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -49,14 +49,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 822064eb43..9169bc6fab 100644
--- a/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -54,14 +54,7 @@ This example demonstrates how to use OIDC with the official action to request a
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/content/actions/learn-github-actions/expressions.md b/content/actions/learn-github-actions/expressions.md
index 536477355b..688638827a 100644
--- a/content/actions/learn-github-actions/expressions.md
+++ b/content/actions/learn-github-actions/expressions.md
@@ -55,7 +55,7 @@ As part of an expression, you can use `boolean`, `null`, `number`, or `string` d
 | `boolean` | `true` or `false` |
 | `null`    | `null` |
 | `number`  | Any number format supported by JSON. |
-| `string`  | You don't need to enclose strings in {% raw %}${{{% endraw %} and {% raw %}}}{% endraw %}. However, if you do, you must use single quotes around the string and escape literal single quotes with an additional single quote. |
+| `string`  | You don't need to enclose strings in `{% raw %}${{{% endraw %}` and `{% raw %}}}{% endraw %}`. However, if you do, you must use single quotes (`'`) around the string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
 
 #### Example
 
diff --git a/content/actions/using-workflows/events-that-trigger-workflows.md b/content/actions/using-workflows/events-that-trigger-workflows.md
index 2a3cb344d0..1ab3cac125 100644
--- a/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -917,8 +917,6 @@ on:
 ```yaml
 on:
   push:
-    types:
-      - opened
     branches:    
       - 'releases/**'
     paths:
@@ -960,8 +958,6 @@ on:
 ```yaml
 on:
   push:
-    types:
-      - opened
     branches:    
       - 'releases/**'
     paths:
@@ -998,7 +994,7 @@ on:
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
 | --------------------- | -------------- | ------------ | -------------|
-| [`release`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag of release |
+| [`release`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag ref of release `refs/tags/<tag_name>` |
 
 {% note %}
 
diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index fc1948522f..f3c3379e0b 100644
--- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -830,7 +830,7 @@ services:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
-      password: ${{ secrets.ghcr_token }}
+      password: ${{ secrets.github_token }}
   myservice2:
     image: dockerhub_org/myservice2
     credentials:
@@ -973,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.<push>
 | `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`<br/><br/>`every/tag` |
 | `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature` |
 | `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`<br/><br/>`v2.0.0` |
+| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2. | `v1.10.1`<br/><br/>`v2.0.0` |
 
 ### Patterns to match file paths
 
diff --git a/content/admin/configuration/configuring-network-settings/configuring-tls.md b/content/admin/configuration/configuring-network-settings/configuring-tls.md
index e3a251095c..33ebb49248 100644
--- a/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -37,6 +37,8 @@ You can generate a certificate signing request (CSR) for your instance using the
 
 ## Uploading a custom TLS certificate
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
@@ -69,6 +71,8 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 7a347ea3ce..afe9132dfc 100644
--- a/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -136,5 +136,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 You can use these additional options with `ghe-restore` command:
-- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - The `-s` flag allows you to select a different backup snapshot.
diff --git a/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index e0987ad337..8f9f359c87 100644
--- a/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -88,8 +88,7 @@ settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-all
 4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery).
 5. When the test email succeeds, at the bottom of the page, click **Save settings**.
 ![Save settings button](/assets/images/enterprise/management-console/save-settings.png)
-6. Wait for the configuration run to complete.
-![Configuring your instance](/assets/images/enterprise/management-console/configuration-run.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 ## Configuring DNS and firewall settings to allow incoming emails
 
diff --git a/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
index 81a40ba9f7..31a26cb6ef 100644
--- a/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
+++ b/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
@@ -34,7 +34,7 @@ High Availability (HA) and Clustering both provide redundancy by eliminating the
 
 ## Backups and disaster recovery
 
-Neither HA or Clustering should be considered a replacement for regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)."
+Neither HA nor Clustering should be considered a replacement for regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)."
 
 ## Monitoring
 
diff --git a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index 37dc21a2f1..a801d41d3f 100644
--- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -15,8 +15,6 @@ redirect_from:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
-
 ## About SAML single sign-on for enterprise accounts
 
 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
diff --git a/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 48b09b3704..182e146c8e 100644
--- a/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -90,6 +90,9 @@ The `$GITHUB_VIA` variable is available in the pre-receive hook environment when
 | <pre>git refs delete api</pre> | Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation |
 | <pre>git refs update api</pre> | Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation |
 | <pre>git repo contents api</pre> | Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation |
+{%- ifversion ghes > 3.0 %}
+| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
 | <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" |
 | <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
 | <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" |
diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b3629bba82..7fef226524 100644
--- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -17,8 +17,12 @@ shortTitle: Deploy keys
 ---
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
 3. In the left sidebar, click **Deploy keys**.
 ![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
 4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
 	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
 
diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index b734154e2b..2ee94aa74d 100644
--- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -19,7 +19,10 @@ shortTitle: Recover an account with 2FA
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %}
+**Warnings**: 
+
+- {% data reusables.two_fa.support-may-not-help %}
+- {% data reusables.accounts.you-must-know-your-password %}
 
 {% endwarning %}
 
@@ -27,15 +30,21 @@ shortTitle: Recover an account with 2FA
 
 ## Using a two-factor authentication recovery code
 
-Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
 
-{% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Under "Having Problems?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Type one of your recovery codes, then click **Verify**.
-  ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+{% data reusables.two_fa.username-password %}
+
+{% ifversion fpt or ghec %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png)
+{%- else %}
+1. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+1. Type one of your recovery codes, then click **Verify**.
+
+   ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
 ## Authenticating with a fallback number
@@ -45,43 +54,52 @@ If you lose access to your primary TOTP app or phone number, you can provide a t
 
 ## Authenticating with a security key
 
-If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
 
 {% ifversion fpt or ghec %}
 ## Authenticating with a verified device, SSH token, or personal access token
 
-If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+If you know your password for {% data variables.product.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
 
 {% note %}
 
-**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
+**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 1-3 business days. {% data variables.product.company_short %} will not review additional requests submitted during this time.
 
 {% endnote %}
 
 You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
 
-1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
-2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
-  ![Link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-3. Click **I understand, get started** to request a reset of your authentication settings.
-  ![Reset authentication settings button](/assets/images/help/2fa/reset-auth-settings.png)
-4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
-  ![Send one-time password button](/assets/images/help/2fa/send-one-time-password.png)
-5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent.
-  ![One-time password field](/assets/images/help/2fa/one-time-password-field.png)
-6. Click **Verify email address**.
-7. Choose an alternative verification factor.
+1. Type your username and password to prompt authentication.
+
+    {% warning %}
+
+    **Warning**: {% data reusables.accounts.you-must-know-your-password %}
+    
+    {% endwarning %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
+1. To the right of "Locked out?", click **Try recovering your account**.
+
+   ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png)
+1. Click **I understand, get started** to request a reset of your authentication settings.
+
+    ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png)
+1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery.
+
+   ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png)
+1. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent.
+
+   ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png)
+1. Click **Verify email address**.
+
+   ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png)
+1. Choose an alternative verification factor.
     - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
     - If you've previously set up a personal access token and would like to use the personal access token for verification, click **Personal access token**.
-  ![Alternative verification buttons](/assets/images/help/2fa/alt-verifications.png)
-8. A member of {% data variables.contact.github_support %} will review your request and email you within 3-5 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
+
+   ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
+1. A member of {% data variables.contact.github_support %} will review your request and email you within 1-3 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
 
 {% endif %}
-
-## Further reading
-
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index b749ca5f27..7747b61120 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -126,7 +126,7 @@ You can search the list of alerts. This is useful if there is a large number of
 
 {% endif %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index c1ea916c94..ca23913fcb 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -5,9 +5,7 @@ intro: You can add code scanning alerts to issues using task lists. This makes i
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
-  fpt: '*'
-  ghes: '> 3.3'
-  ghae: issue-5036
+  feature: 'code-scanning-task-lists'
 type: how_to
 topics:
   - Advanced Security
diff --git a/content/code-security/getting-started/github-security-features.md b/content/code-security/getting-started/github-security-features.md
index 646ed3ccd5..b4db279d0b 100644
--- a/content/code-security/getting-started/github-security-features.md
+++ b/content/code-security/getting-started/github-security-features.md
@@ -25,7 +25,7 @@ The {% data variables.product.prodname_advisory_database %} contains a curated l
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ### Security policy
-  
+
 Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
 {% endif %}
 
@@ -74,7 +74,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi
 
 ### {% data variables.product.prodname_secret_scanning_caps %}
 
-Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %} 
+Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %}
 {%- ifversion ghec or ghes or ghae %}
 {% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
 
@@ -84,6 +84,12 @@ Automatically detect tokens or credentials that have been checked into a reposit
 Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
 {% endif %}
 
+{% ifversion ghec or ghes > 3.1 %}
+### Security overview
+
+Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+{% endif %}
+
 ## Further reading
 - "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
 - "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index 0e1ebb5530..4d52202c79 100644
--- a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,7 +27,6 @@ You can also block users. For more information, see "[Blocking a user from your
 ## Limiting interactions for your user account
 
 {% data reusables.user_settings.access_settings %}
-1. In your user settings sidebar, under "Moderation settings", click **Interaction limits**.
-  !["Interaction limits" tab in the user settings sidebar](/assets/images/help/settings/settings-sidebar-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![Temporary interaction limit options](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index 6c3a6932c0..a9084bef8f 100644
--- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -40,7 +40,7 @@ You can set the following top-level keys for each issue form.
 | `description` | A description for the issue form template, which appears in the template chooser interface. | Required | String |
 | `body` | Definition of the input types in the form. | Required | Array |
 | `assignees` | People who will be automatically assigned to issues created with this template. | Optional | Array or comma-delimited string |
-| `labels` | Labels that will automatically be added to issues created with this template. | Optional | String |
+| `labels` | Labels that will automatically be added to issues created with this template. | Optional | Array or comma-delimited string |
 | `title` | A default title that will be pre-populated in the issue submission form. | Optional | String |
 
 For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)."
diff --git a/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index d390f9c8e5..2779cd7e7f 100644
--- a/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -298,10 +298,10 @@ subdirectory of the callback URL.
 
 The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app.
 
-For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
+For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`:
 
 ```
-http://localhost:1234/path
+http://127.0.0.1:1234/path
 ```
 
 ## Creating multiple tokens for OAuth Apps
diff --git a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 843ec9a968..d0491e93f6 100644
--- a/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -25,13 +25,9 @@ shortTitle: Enterprise Cloud trial
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
-{% data reusables.saml.saml-accounts %}
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
 
-For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
-
-{% data reusables.enterprise-accounts.emu-short-summary %}
-
-{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
 
 {% data reusables.products.which-product-to-use %}
 
@@ -41,7 +37,11 @@ You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe
 
 Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
 
-Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
 
 ## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
 
@@ -64,11 +64,13 @@ After setting up your trial, you can explore {% data variables.product.prodname_
 
 ## Finishing your trial
 
-You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
 
-If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}. 
 
-Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/issues/tracking-your-work-with-issues/about-task-lists.md b/content/issues/tracking-your-work-with-issues/about-task-lists.md
index c2169827fe..637086f77e 100644
--- a/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -76,5 +76,5 @@ Any issues that are referenced in a task list specify that they are tracked by t
 
 ## Further reading
 
-* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% if code-scanning-task-lists %}
 * "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index d4ad5f88ae..80e960d30c 100644
--- a/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -153,7 +153,7 @@ Query parameter | Example
 `projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` creates an issue with the title "Bug fix" and adds it to the organization's project board 1.
 `template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` creates an issue with a template in the issue body. The `template` query parameter works with templates stored in an `ISSUE_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 841dca73ea..134d90e67d 100644
--- a/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -23,6 +23,7 @@ If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index df0ef33659..81b5d7e548 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -23,8 +23,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
 ## Verifying a domain for your user site
 
 {% data reusables.user_settings.access_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
@@ -38,8 +37,7 @@ Organization owners can verify custom domains for their organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
diff --git a/content/rest/guides/delivering-deployments.md b/content/rest/guides/delivering-deployments.md
index 13ad16c3da..44be60c989 100644
--- a/content/rest/guides/delivering-deployments.md
+++ b/content/rest/guides/delivering-deployments.md
@@ -24,7 +24,7 @@ the moment your code lands on the default branch.
 This guide will use that API to demonstrate a setup that you can use.
 In our scenario, we will:
 
-* Merge a pull request
+* Merge a pull request.
 * When the CI is finished, we'll set the pull request's status accordingly.
 * When the pull request is merged, we'll run our deployment to our server.
 
diff --git a/content/rest/reference/enterprise-admin.md b/content/rest/reference/enterprise-admin.md
index d903396303..006d78ee79 100644
--- a/content/rest/reference/enterprise-admin.md
+++ b/content/rest/reference/enterprise-admin.md
@@ -68,7 +68,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer
 
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5528 %}
 
 ## Audit log
 
diff --git a/content/rest/reference/permissions-required-for-github-apps.md b/content/rest/reference/permissions-required-for-github-apps.md
index 83e56e3043..b730f97658 100644
--- a/content/rest/reference/permissions-required-for-github-apps.md
+++ b/content/rest/reference/permissions-required-for-github-apps.md
@@ -921,6 +921,9 @@ _Teams_
 {% ifversion fpt or ghes > 3.0 or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (:read)
 {% endif -%}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5435 -%}
+- [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (:read)
+{% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
 ### Permission on "self-hosted runners"
diff --git a/crowdin.yml b/crowdin.yml
index 583a161797..6c597c3158 100644
--- a/crowdin.yml
+++ b/crowdin.yml
@@ -1,6 +1,8 @@
 files:
   - source: /content/**/*.md
     translation: /translations/%locale%/%original_path%/%original_file_name%
+    # See lib/page-data.js for a matching list of prefix exceptions
+    # Try to keep these in sync when editing in either location.
     ignore:
       - '/content/README.md'
       - '/content/early-access'
diff --git a/data/features/code-scanning-task-lists.yml b/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..29408f5d1f
--- /dev/null
+++ b/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/data/reusables/accounts/you-must-know-your-password.md b/data/reusables/accounts/you-must-know-your-password.md
new file mode 100644
index 0000000000..f4795c3909
--- /dev/null
+++ b/data/reusables/accounts/you-must-know-your-password.md
@@ -0,0 +1 @@
+If you protect your personal account with two-factor authentication but do not know your password, you will not be able to generate a one-time password to recover your account. {% data variables.product.company_short %} can send a password reset email to a verified address associated with your account. For more information, see "[Updating your {% data variables.product.prodname_dotcom %} access credentials](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)."
diff --git a/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
index faa8c4bf37..bbfb2613a4 100644
--- a/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
+++ b/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
@@ -8,6 +8,6 @@ container:
   image: ghcr.io/owner/image
   credentials:
      username: ${{ github.actor }}
-     password: ${{ secrets.ghcr_token }}
+     password: ${{ secrets.github_token }}
 ```
 {% endraw %}
diff --git a/data/reusables/actions/oidc-permissions-token.md b/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..8b9c4971f1
--- /dev/null
+++ b/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,13 @@
+The job or workflow run requires a `permissions` setting with [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). This allows the JWT to be requested from GitHub's OIDC provider using one of these approaches:
+
+- Using environment variables on the runner (`ACTIONS_ID_TOKEN_REQUEST_URL` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Using `getIDToken()` from the Actions toolkit.
+
+If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+
+```yaml{:copy}
+permissions:
+  id-token: write
+```
+
+You may need to specify additional permissions here, depending on your workflow's requirements. 
\ No newline at end of file
diff --git a/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
index 7db5b9879a..6664cbfafc 100644
--- a/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
+++ b/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 
 {% note %}
 
diff --git a/data/reusables/enterprise_management_console/save-settings.md b/data/reusables/enterprise_management_console/save-settings.md
index 8178f09d08..2ed1c07799 100644
--- a/data/reusables/enterprise_management_console/save-settings.md
+++ b/data/reusables/enterprise_management_console/save-settings.md
@@ -1,3 +1,3 @@
 1. Under the left sidebar, click **Save settings**.
   ![The Save settings button in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-1. Wait for the configuration run to complete.
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
\ No newline at end of file
diff --git a/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..a1cc2ae3c0
--- /dev/null
+++ b/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.product.product_location %}.
+
+{% endwarning %}
diff --git a/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..563e7f6f86
--- /dev/null
+++ b/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,3 @@
+1. Wait for the configuration run to complete.
+
+   ![Configuring your instance](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/data/reusables/gated-features/user-repo-collaborators.md b/data/reusables/gated-features/user-repo-collaborators.md
index 111062b8c4..bc2fadb3b3 100644
--- a/data/reusables/gated-features/user-repo-collaborators.md
+++ b/data/reusables/gated-features/user-repo-collaborators.md
@@ -1 +1,3 @@
+{% ifversion fpt %}
 If you're using {% data variables.product.prodname_free_user %}, you can add unlimited collaborators on public and private repositories.
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/organizations/billing-settings.md b/data/reusables/organizations/billing-settings.md
index 45d230b82a..feb35fd556 100644
--- a/data/reusables/organizations/billing-settings.md
+++ b/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
 {% data reusables.user_settings.access_settings %}
-2. In the settings sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% data reusables.profile.org_settings %}
-1. If you're an organization owner, in the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/data/reusables/organizations/oauth_app_access.md b/data/reusables/organizations/oauth_app_access.md
index 7155b3a2c6..a2dc8773f5 100644
--- a/data/reusables/organizations/oauth_app_access.md
+++ b/data/reusables/organizations/oauth_app_access.md
@@ -1,4 +1 @@
-{% ifversion fpt or ghec %}
-  1. In the Settings sidebar, click **Third-party access**.
-  ![{% data variables.product.prodname_oauth_app %} access tab in the left sidebar](/assets/images/help/settings/settings-sidebar-third-party-access.png)
-{% endif %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
diff --git a/data/reusables/organizations/teams_sidebar.md b/data/reusables/organizations/teams_sidebar.md
index 06610117ff..338fe6bc8e 100644
--- a/data/reusables/organizations/teams_sidebar.md
+++ b/data/reusables/organizations/teams_sidebar.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
 1. In the Settings sidebar, click **Teams**.
   ![Teams tab in the organization settings sidebar](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/data/reusables/profile/org_member_privileges.md b/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..7594cff95f
--- /dev/null
+++ b/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1,2 @@
+3. Under "Access", click **Member privileges**.
+     ![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png) 
diff --git a/data/reusables/repositories/actions-scheduled-workflow-example.md b/data/reusables/repositories/actions-scheduled-workflow-example.md
index d61c5baa10..408d023293 100644
--- a/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -1,4 +1,4 @@
-You can schedule a workflow to run at specific UTC times using [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 15 minutes.
+You can schedule a workflow to run at specific UTC times using [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 5 minutes.
 
 This example triggers the workflow every day at 5:30 and 17:30 UTC:
 
diff --git a/data/reusables/repositories/sidebar-notifications.md b/data/reusables/repositories/sidebar-notifications.md
index 477534215c..1a5edf0d3d 100644
--- a/data/reusables/repositories/sidebar-notifications.md
+++ b/data/reusables/repositories/sidebar-notifications.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
 1. Click **Notifications**.
 ![Notifications button in sidebar](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/data/reusables/user-settings/oauth_apps.md b/data/reusables/user-settings/oauth_apps.md
index dca540647b..c38ffb6e9c 100644
--- a/data/reusables/user-settings/oauth_apps.md
+++ b/data/reusables/user-settings/oauth_apps.md
@@ -1,2 +1,2 @@
-1. In the left sidebar, click **OAuth Apps**.
+1. In the left sidebar, click **{% data variables.product.prodname_oauth_apps %}**.
 ![OAuth Apps section](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/data/reusables/user_settings/access_applications.md b/data/reusables/user_settings/access_applications.md
index 2339cdfad9..efc6abe024 100644
--- a/data/reusables/user_settings/access_applications.md
+++ b/data/reusables/user_settings/access_applications.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
 1. In the left sidebar, click **Applications**.
 ![Applications tab](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/data/reusables/user_settings/accessibility_settings.md b/data/reusables/user_settings/accessibility_settings.md
index 073c3c1456..2c9e37e2f4 100644
--- a/data/reusables/user_settings/accessibility_settings.md
+++ b/data/reusables/user_settings/accessibility_settings.md
@@ -1,2 +1 @@
-1. In the navigation on the left hand side, click the **Accessibility** link.
-![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)
+1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**.
diff --git a/data/reusables/user_settings/account_settings.md b/data/reusables/user_settings/account_settings.md
index 40e288bb68..7edd6e2f14 100644
--- a/data/reusables/user_settings/account_settings.md
+++ b/data/reusables/user_settings/account_settings.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
+{% else %}
 1. In the left sidebar, click **Account**.
 ![Account settings menu option](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/data/reusables/user_settings/appearance-settings.md b/data/reusables/user_settings/appearance-settings.md
index 5850d7a583..d201a2de59 100644
--- a/data/reusables/user_settings/appearance-settings.md
+++ b/data/reusables/user_settings/appearance-settings.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
 1. In the user settings sidebar, click **Appearance**.
 
-   !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
+   !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/user_settings/billing_plans.md b/data/reusables/user_settings/billing_plans.md
index 505b2eb273..333102205b 100644
--- a/data/reusables/user_settings/billing_plans.md
+++ b/data/reusables/user_settings/billing_plans.md
@@ -1,2 +1 @@
-1. In your user settings sidebar, click **Billing & plans**.
-![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/data/reusables/user_settings/blocked_users.md b/data/reusables/user_settings/blocked_users.md
index 5a9a5dfc68..b7ba502dca 100644
--- a/data/reusables/user_settings/blocked_users.md
+++ b/data/reusables/user_settings/blocked_users.md
@@ -1,2 +1 @@
-1. In your user settings sidebar, click **Blocked users** under **Moderation settings**.
-![Blocked users tab](/assets/images/help/settings/settings-sidebar-blocked-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**.
diff --git a/data/reusables/user_settings/codespaces-tab.md b/data/reusables/user_settings/codespaces-tab.md
index 4ae4e90467..5aa532885e 100644
--- a/data/reusables/user_settings/codespaces-tab.md
+++ b/data/reusables/user_settings/codespaces-tab.md
@@ -1,2 +1 @@
-1. In the left sidebar, click **Codespaces**.
-![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/data/reusables/user_settings/developer_settings.md b/data/reusables/user_settings/developer_settings.md
index a6f9341acf..f8fc22316f 100644
--- a/data/reusables/user_settings/developer_settings.md
+++ b/data/reusables/user_settings/developer_settings.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %} 
 1. In the left sidebar, click **Developer settings**.
 ![Developer settings](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/data/reusables/user_settings/emails.md b/data/reusables/user_settings/emails.md
index 8f20630240..dd47cf76a9 100644
--- a/data/reusables/user_settings/emails.md
+++ b/data/reusables/user_settings/emails.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
 1. In the left sidebar, click **Emails**.
 ![Emails tab](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/data/reusables/user_settings/organizations.md b/data/reusables/user_settings/organizations.md
index 38d7cb271d..cf4c3cf6c5 100644
--- a/data/reusables/user_settings/organizations.md
+++ b/data/reusables/user_settings/organizations.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
 1. In your user settings sidebar, click **Organizations**.
 ![User settings for organizations](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/data/reusables/user_settings/repo-tab.md b/data/reusables/user_settings/repo-tab.md
index 659e54e23f..be39213129 100644
--- a/data/reusables/user_settings/repo-tab.md
+++ b/data/reusables/user_settings/repo-tab.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 1. In the left sidebar, click **Repositories**.
   ![Repositories tab](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/data/reusables/user_settings/saved_replies.md b/data/reusables/user_settings/saved_replies.md
index d06be8e48c..0d007727eb 100644
--- a/data/reusables/user_settings/saved_replies.md
+++ b/data/reusables/user_settings/saved_replies.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
 1. In the left sidebar, click **Saved replies**.
 ![Saved replies tab](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/data/reusables/user_settings/security-analysis.md b/data/reusables/user_settings/security-analysis.md
index 028582904c..0f79b730ae 100644
--- a/data/reusables/user_settings/security-analysis.md
+++ b/data/reusables/user_settings/security-analysis.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
 1. In the left sidebar, click **Security & analysis**.
 ![Security and analysis settings](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/data/reusables/user_settings/security.md b/data/reusables/user_settings/security.md
index a0c24abf4b..56cc87e20a 100644
--- a/data/reusables/user_settings/security.md
+++ b/data/reusables/user_settings/security.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
 1. In the left sidebar, click **Account security**.
 ![User account security settings](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/data/reusables/user_settings/ssh.md b/data/reusables/user_settings/ssh.md
index 09d83b45f4..08e50ade35 100644
--- a/data/reusables/user_settings/ssh.md
+++ b/data/reusables/user_settings/ssh.md
@@ -1,2 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
 1. In the user settings sidebar, click **SSH and GPG keys**.
 ![Authentication keys](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/data/ui.yml b/data/ui.yml
index 648a99dde5..0ecf614874 100644
--- a/data/ui.yml
+++ b/data/ui.yml
@@ -53,7 +53,7 @@ pages:
   article_version: 'Article version'
   miniToc: In this article
   contributor_callout: This article is contributed and maintained by
-  all_enterprise_releases: All Enterprise releases
+  all_enterprise_releases: All Enterprise Server releases
 errors:
   oops: Ooops!
   something_went_wrong: It looks like something went wrong.
diff --git a/docker-compose.prod.tmpl.yaml b/docker-compose.prod.tmpl.yaml
index d5b1be6601..75860f3884 100644
--- a/docker-compose.prod.tmpl.yaml
+++ b/docker-compose.prod.tmpl.yaml
@@ -12,7 +12,6 @@ services:
       HYDRO_ENDPOINT: ${HYDRO_ENDPOINT}
       HYDRO_SECRET: ${HYDRO_SECRET}
       HAYSTACK_URL: ${HAYSTACK_URL}
-      WEB_CONCURRENCY: ${WEB_CONCURRENCY}
       HEROKU_APP_NAME: ${HEROKU_APP_NAME}
       ENABLED_LANGUAGES: ${ENABLED_LANGUAGES}
       DEPLOYMENT_ENV: ${DEPLOYMENT_ENV}
diff --git a/lib/create-tree.js b/lib/create-tree.js
index e2b02ea267..aa83243649 100644
--- a/lib/create-tree.js
+++ b/lib/create-tree.js
@@ -8,7 +8,7 @@ const __dirname = path.dirname(fileURLToPath(import.meta.url))
 const _basePaths = new Map()
 // Return a full directory based on __dirname from a specific language directory.
 // This function is memoized with a simple global cache object.
-function getBasePath(directory) {
+export function getBasePath(directory) {
   if (!_basePaths.has(directory)) {
     _basePaths.set(directory, path.posix.join(__dirname, '..', directory, 'content'))
   }
diff --git a/lib/page-data.js b/lib/page-data.js
index e5ac95f2ba..b1fa1c7ad1 100644
--- a/lib/page-data.js
+++ b/lib/page-data.js
@@ -2,15 +2,29 @@ import { fileURLToPath } from 'url'
 import path from 'path'
 import languages from './languages.js'
 import { allVersions } from './all-versions.js'
-import createTree from './create-tree.js'
+import createTree, { getBasePath } from './create-tree.js'
 import renderContent from './render-content/index.js'
 import loadSiteData from './site-data.js'
 import nonEnterpriseDefaultVersion from './non-enterprise-default-version.js'
+import Page from './page.js'
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
 const versions = Object.keys(allVersions)
 const enterpriseServerVersions = versions.filter((v) => v.startsWith('enterprise-server@'))
 const renderOpts = { textOnly: true, encodeEntities: true }
 
+// These are the exceptions to the rule.
+// These URI prefixes should match what you'll find in crowdin.yml.
+// If a URI starts with one of these prefixes, it basically means we don't
+// bother to "backfill" a translation in its spot.
+// For example, `/en/github/site-policy-deprecated/foo` works
+// only in English and we don't bother making `/ja/github/site-policy-deprecated/foo`
+// work too.
+const TRANSLATION_DRIFT_EXCEPTIONS = [
+  'github/site-policy-deprecated',
+  // Early access stuff never has translations.
+  'early-access',
+]
+
 /**
  * We only need to initialize pages _once per language_ since pages don't change per version. So we do that
  * first since it's the most expensive work. This gets us a nested object with pages attached that we can use
@@ -152,8 +166,101 @@ export function createMapFromArray(pageList) {
 }
 
 export async function loadPageMap(pageList) {
-  const pages = pageList || (await loadPageList())
-  return createMapFromArray(pages)
+  const pages = await correctTranslationOrphans(pageList || (await loadPageList()))
+  const pageMap = createMapFromArray(pages)
+  return pageMap
+}
+
+// If a translation page exists, that doesn't have an English equivalent,
+// remove it.
+// If an English page exists, that doesn't have an translation equivalent,
+// add it.
+// Note, this function is exported purely for the benefit of the unit tests.
+export async function correctTranslationOrphans(pageList, basePath = null) {
+  const englishRelativePaths = new Set()
+  for (const page of pageList) {
+    if (page.languageCode === 'en') {
+      englishRelativePaths.add(page.relativePath)
+    }
+  }
+
+  // Prime the Map with an empty set for each language prefix.
+  // It's important that we do this for *every* language rather than
+  // just populating `nonEnglish` based on those pages that *are* present.
+  // Otherwise, we won't have an index of all the languages
+  // that *might* be missing.
+  const nonEnglish = new Map()
+  Object.keys(languages)
+    .filter((lang) => lang !== 'en')
+    .forEach((languageCode) => {
+      nonEnglish.set(languageCode, new Set())
+    })
+
+  // By default, when backfilling, we set the `basePath` to be that of
+  // English. But for the benefit of being able to do unit tests,
+  // we make this an optional argument. Then, unit tests can use
+  // its "tests/fixtures" directory.
+  const englishBasePath = basePath || getBasePath(languages.en.dir)
+
+  // Filter out all non-English pages that appear to be excess.
+  // E.g. if an English doc was renamed from `content/foo.md` to
+  // `content/bar.md` what will happen is that `translations/*/content/foo.md`
+  // will still linger around and we want to remove that even if it was
+  // scooped up from disk.
+  const newPageList = []
+  for (const page of pageList) {
+    if (page.languageCode === 'en') {
+      // English pages are never considered "excess"
+      newPageList.push(page)
+      continue
+    }
+
+    // If this translation page exists in English, keep it but also
+    // add it to the set of relative paths that is known.
+    if (englishRelativePaths.has(page.relativePath)) {
+      nonEnglish.get(page.languageCode).add(page.relativePath)
+      newPageList.push(page)
+      continue
+    }
+  }
+
+  const pageLoadPromises = []
+  for (const relativePath of englishRelativePaths) {
+    for (const [languageCode, relativePaths] of nonEnglish) {
+      if (!relativePaths.has(relativePath)) {
+        // At this point, we've found an English `relativePath` that is
+        // not used by this language.
+        // But before we decide to "backfill" it from the English equivalent
+        // we first need to figure out if it should be excluded.
+        // The reason for doing this check this late is for the benefit
+        // of optimization. In general, when the translation pipeline has
+        // done its magic, this should be very rare, so it's unnecessary
+        // to do this exception check on every single English relativePath.
+        if (TRANSLATION_DRIFT_EXCEPTIONS.find((exception) => relativePath.startsWith(exception))) {
+          continue
+        }
+
+        // The magic right here!
+        // The trick is that we can't clone instances of class Page. We need
+        // to create them for this language. But the trick is that we
+        // use the English relative path so it can have something to read.
+        // For example, if we have figured out that
+        // `translations/ja-JP/content/foo.md` doesn't exist, we pretend
+        // that we can use `foo.md` and the base path of `content/`.
+        pageLoadPromises.push(
+          Page.init({
+            basePath: englishBasePath,
+            relativePath: relativePath,
+            languageCode: languageCode,
+          })
+        )
+      }
+    }
+  }
+  const additionalPages = await Promise.all(pageLoadPromises)
+  newPageList.push(...additionalPages)
+
+  return newPageList
 }
 
 export default {
diff --git a/lib/page.js b/lib/page.js
index 20a1e48cce..b0a3625a9e 100644
--- a/lib/page.js
+++ b/lib/page.js
@@ -228,12 +228,12 @@ class Page {
     }
 
     // product frontmatter may contain liquid
-    if (this.product) {
+    if (this.rawProduct) {
       this.product = await renderContentCacheByContext('product')(this.rawProduct, context)
     }
 
     // permissions frontmatter may contain liquid
-    if (this.permissions) {
+    if (this.rawPermissions) {
       this.permissions = await renderContentCacheByContext('permissions')(
         this.rawPermissions,
         context
@@ -241,7 +241,7 @@ class Page {
     }
 
     // Learning tracks may contain Liquid and need to have versioning processed.
-    if (this.learningTracks) {
+    if (this.rawLearningTracks) {
       const { featuredTrack, learningTracks } = await processLearningTracks(
         this.rawLearningTracks,
         context
diff --git a/lib/prefix-stream-write.js b/lib/prefix-stream-write.js
deleted file mode 100644
index 0cb4610b8e..0000000000
--- a/lib/prefix-stream-write.js
+++ /dev/null
@@ -1,25 +0,0 @@
-export default function prefixStreamWrite(writableStream, prefix) {
-  const oldWrite = writableStream.write
-
-  function newWrite(...args) {
-    const [chunk, encoding] = args
-
-    // Prepend the prefix if the chunk is either a string or a Buffer.
-    // Otherwise, just leave it alone to be safe.
-    if (typeof chunk === 'string') {
-      // Only prepend the prefix is the `encoding` is safe or not provided.
-      // If it's a function, it is third arg `callback` provided as optional second
-      if (!encoding || encoding === 'utf8' || typeof encoding === 'function') {
-        args[0] = prefix + chunk
-      }
-    } else if (Buffer.isBuffer(chunk)) {
-      args[0] = Buffer.concat([Buffer.from(prefix), chunk])
-    }
-
-    return oldWrite.apply(this, args)
-  }
-
-  writableStream.write = newWrite
-
-  return writableStream
-}
diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index a0513b2b20..16403520cd 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -19177,7 +19177,7 @@
       }
     ],
     "summary": "Get the audit log for an organization",
-    "description": "Gets the audit log for an organization. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization).\"\n\nTo use this endpoint, you must be an organization owner, and you must use an access token with the `admin:org` scope. GitHub Apps must have the `organization_administration` read permission to use this endpoint.",
+    "description": "Gets the audit log for an organization. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization).\"\n\nThis endpoint is available for organizations on GitHub Enterprise Cloud. To use this endpoint, you must be an organization owner, and you must use an access token with the `admin:org` scope. GitHub Apps must have the `organization_administration` read permission to use this endpoint.",
     "operationId": "orgs/get-audit-log",
     "tags": [
       "orgs"
@@ -19197,7 +19197,7 @@
     "categoryLabel": "Orgs",
     "notes": [],
     "bodyParameters": [],
-    "descriptionHTML": "<p>Gets the audit log for an organization. For more information, see \"<a href=\"https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization\">Reviewing the audit log for your organization</a>.\"</p>\n<p>To use this endpoint, you must be an organization owner, and you must use an access token with the <code>admin:org</code> scope. GitHub Apps must have the <code>organization_administration</code> read permission to use this endpoint.</p>",
+    "descriptionHTML": "<p>Gets the audit log for an organization. For more information, see \"<a href=\"https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization\">Reviewing the audit log for your organization</a>.\"</p>\n<p>This endpoint is available for organizations on GitHub Enterprise Cloud. To use this endpoint, you must be an organization owner, and you must use an access token with the <code>admin:org</code> scope. GitHub Apps must have the <code>organization_administration</code> read permission to use this endpoint.</p>",
     "responses": [
       {
         "httpStatusCode": "200",
@@ -19486,6 +19486,166 @@
       }
     ]
   },
+  {
+    "verb": "get",
+    "requestPath": "/orgs/{org}/code-scanning/alerts",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "before",
+        "description": "A cursor, as given in the [Link header](https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events before this cursor.",
+        "in": "query",
+        "required": false,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>A cursor, as given in the <a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header\">Link header</a>. If specified, the query only searches for events before this cursor.</p>"
+      },
+      {
+        "name": "after",
+        "description": "A cursor, as given in the [Link header](https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events after this cursor.",
+        "in": "query",
+        "required": false,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>A cursor, as given in the <a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header\">Link header</a>. If specified, the query only searches for events after this cursor.</p>"
+      },
+      {
+        "name": "page",
+        "description": "Page number of the results to fetch.",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 1
+        },
+        "descriptionHTML": "<p>Page number of the results to fetch.</p>"
+      },
+      {
+        "name": "per_page",
+        "description": "Results per page (max 100)",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 30
+        },
+        "descriptionHTML": "<p>Results per page (max 100)</p>"
+      },
+      {
+        "name": "direction",
+        "description": "One of `asc` (ascending) or `desc` (descending).",
+        "in": "query",
+        "required": false,
+        "schema": {
+          "type": "string",
+          "enum": [
+            "asc",
+            "desc"
+          ],
+          "default": "desc"
+        },
+        "descriptionHTML": "<p>One of <code>asc</code> (ascending) or <code>desc</code> (descending).</p>"
+      },
+      {
+        "name": "state",
+        "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.",
+        "in": "query",
+        "required": false,
+        "schema": {
+          "type": "string",
+          "description": "State of a code scanning alert.",
+          "enum": [
+            "open",
+            "closed",
+            "dismissed",
+            "fixed"
+          ]
+        },
+        "descriptionHTML": "<p>Set to <code>open</code>, <code>fixed</code>, or <code>dismissed</code> to list code scanning alerts in a specific state.</p>"
+      },
+      {
+        "name": "sort",
+        "description": "Can be one of `created`, `updated`.",
+        "in": "query",
+        "required": false,
+        "schema": {
+          "type": "string",
+          "enum": [
+            "created",
+            "updated"
+          ],
+          "default": "created"
+        },
+        "descriptionHTML": "<p>Can be one of <code>created</code>, <code>updated</code>.</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/code-scanning/alerts",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/code-scanning/alerts</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /orgs/{org}/code-scanning/alerts', {\n  org: 'org'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /orgs/{org}/code-scanning/alerts'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List code scanning alerts for an organization",
+    "description": "Lists all code scanning alerts for the default branch (usually `main`\nor `master`) for all eligible repositories in an organization.\nTo use this endpoint, you must be an administrator for the repository or organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `code_scanning_alerts` read permission to use this endpoint.",
+    "tags": [
+      "code-scanning"
+    ],
+    "operationId": "code-scanning/list-alerts-for-org",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/code-scanning#list-code-scanning-alerts-by-organization"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "code-scanning",
+      "subcategory": null
+    },
+    "slug": "list-code-scanning-alerts-for-an-organization",
+    "category": "code-scanning",
+    "categoryLabel": "Code scanning",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists all code scanning alerts for the default branch (usually <code>main</code>\nor <code>master</code>) for all eligible repositories in an organization.\nTo use this endpoint, you must be an administrator for the repository or organization, and you must use an access token with the <code>repo</code> scope or <code>security_events</code> scope.</p>\n<p>GitHub Apps must have the <code>code_scanning_alerts</code> read permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "<p>Response</p>",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">[</span>\n  <span class=\"hljs-punctuation\">{</span>\n    <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">4</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-02-13T12:29:18Z\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/4\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/hello-world/code-scanning/4\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"state\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"open\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_by\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_reason\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"rule\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"js/zipslip\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"severity\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"error\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"tags\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"security\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"external/cwe/cwe-022\"</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Arbitrary file write during zip extraction\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"js/zipslip\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"tool\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"CodeQL\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"guid\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"version\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2.4.0\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"most_recent_instance\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"ref\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"refs/heads/main\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"analysis_key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\".github/workflows/codeql-analysis.yml:CodeQL-Build\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"environment\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"{}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"state\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"open\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"commit_sha\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"39406e42cb832f683daa691dd652a8dc36ee8930\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"message\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"text\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This path depends on a user-provided value.\"</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"location\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"path\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"spec-main/api-session-spec.ts\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"start_line\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">917</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"end_line\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">917</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"start_column\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">7</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"end_column\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">18</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"classifications\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"test\"</span>\n      <span class=\"hljs-punctuation\">]</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"instances_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/4/instances\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/forks\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/languages\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/merges\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/tags\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/teams\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"clone_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"mirror_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:git.example.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/hooks\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"svn_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://svn.github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"homepage\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"language\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"forks_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"stargazers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"watchers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"size\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">108</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"default_branch\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"master\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"open_issues_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"is_template\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"topics\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"atom\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"electron\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"api\"</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_projects\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_wiki\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_pages\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_downloads\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"archived\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"disabled\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"public\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"pushed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:06:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:01:12Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:14:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"permissions\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"push\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pull\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"template_repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/events\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/forks\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/languages\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/merges\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/tags\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/teams\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"clone_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"mirror_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:git.example.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/hooks\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"svn_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://svn.github.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"homepage\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"language\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"stargazers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"watchers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"watchers\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"size\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">108</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"default_branch\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"master\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"open_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"open_issues_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"is_template\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"license\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"mit\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MIT License\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/licenses/mit\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"spdx_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MIT\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDc6TGljZW5zZW1pdA==\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/licenses/mit\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"topics\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n          <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"atom\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"electron\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"api\"</span>\n        <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_projects\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_wiki\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_pages\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_downloads\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"archived\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"disabled\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"public\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pushed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:06:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:01:12Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:14:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"permissions\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"push\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"pull\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_rebase_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"temp_clone_token\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"ABTLWHOULUVAXGTRYU7OC2876QJ2O\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_squash_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_auto_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"delete_branch_on_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_merge_commit\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscribers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">42</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"network_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span>\n      <span class=\"hljs-punctuation\">}</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-punctuation\">{</span>\n    <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">3</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-02-13T12:29:18Z\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/3\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/hello-world/code-scanning/3\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"state\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"dismissed\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_by\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-02-14T12:29:18Z\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"dismissed_reason\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"false positive\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"rule\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"js/zipslip\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"severity\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"error\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"tags\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"security\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"external/cwe/cwe-022\"</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Arbitrary file write during zip extraction\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"js/zipslip\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"tool\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"CodeQL\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"guid\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"version\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2.4.0\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"most_recent_instance\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"ref\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"refs/heads/main\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"analysis_key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\".github/workflows/codeql-analysis.yml:CodeQL-Build\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"environment\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"{}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"state\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"open\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"commit_sha\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"39406e42cb832f683daa691dd652a8dc36ee8930\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"message\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"text\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This path depends on a user-provided value.\"</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"location\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"path\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"lib/ab12-gen.js\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"start_line\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">917</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"end_line\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">917</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"start_column\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">7</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"end_column\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">18</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"classifications\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span><span class=\"hljs-punctuation\">]</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"instances_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/3/instances\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/forks\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/languages\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/merges\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/tags\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/teams\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"clone_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"mirror_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:git.example.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/hooks\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"svn_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://svn.github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"homepage\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"language\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"forks_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"stargazers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"watchers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"size\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">108</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"default_branch\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"master\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"open_issues_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"is_template\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"topics\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"atom\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"electron\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"api\"</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_projects\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_wiki\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_pages\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"has_downloads\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"archived\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"disabled\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"public\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"pushed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:06:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:01:12Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:14:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"permissions\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"push\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pull\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"template_repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/events\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/forks\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/languages\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/merges\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/tags\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/teams\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"clone_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World-Template.git\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"mirror_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:git.example.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World-Template/hooks\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"svn_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://svn.github.com/octocat/Hello-World-Template\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"homepage\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"language\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"forks_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">9</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"stargazers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"watchers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"watchers\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">80</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"size\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">108</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"default_branch\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"master\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"open_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"open_issues_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"is_template\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"license\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"mit\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MIT License\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/licenses/mit\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"spdx_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MIT\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDc6TGljZW5zZW1pdA==\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/licenses/mit\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"topics\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n          <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"atom\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"electron\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-string\">\"api\"</span>\n        <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_issues\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_projects\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_wiki\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_pages\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"has_downloads\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"archived\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"disabled\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"public\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"pushed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:06:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:01:12Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2011-01-26T19:14:43Z\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"permissions\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"push\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"pull\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_rebase_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"temp_clone_token\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"ABTLWHOULUVAXGTRYU7OC2876QJ2O\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_squash_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_auto_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"delete_branch_on_merge\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"allow_merge_commit\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscribers_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">42</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"network_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">0</span>\n      <span class=\"hljs-punctuation\">}</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">}</span>\n<span class=\"hljs-punctuation\">]</span>\n</code></pre>"
+      },
+      {
+        "httpStatusCode": "403",
+        "httpStatusMessage": "Forbidden",
+        "description": "<p>Response if GitHub Advanced Security is not enabled for this repository</p>"
+      },
+      {
+        "httpStatusCode": "404",
+        "httpStatusMessage": "Not Found",
+        "description": "<p>Resource not found</p>"
+      },
+      {
+        "httpStatusCode": "503",
+        "httpStatusMessage": "Service Unavailable",
+        "description": "<p>Service unavailable</p>"
+      }
+    ]
+  },
   {
     "verb": "get",
     "requestPath": "/orgs/{org}/credential-authorizations",
@@ -27687,17 +27847,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -27717,7 +27876,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -27793,17 +27952,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -37174,13 +37332,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -39829,13 +39988,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -68363,14 +68523,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -68449,14 +68609,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -68547,14 +68707,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -68633,14 +68793,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json
index 39b8d1ca14..66025d6593 100644
--- a/lib/rest/static/decorated/ghes-3.0.json
+++ b/lib/rest/static/decorated/ghes-3.0.json
@@ -25494,17 +25494,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -25515,6 +25514,15 @@
                 "rawType": "integer",
                 "rawDescription": "The ID of a team to set as the parent team.",
                 "childParamsGroups": []
+              },
+              "ldap_dn": {
+                "type": "string",
+                "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+                "name": "ldap_dn",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.0/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.0/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+                "childParamsGroups": []
               }
             },
             "required": [
@@ -25524,7 +25532,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -25600,17 +25608,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -25621,6 +25628,15 @@
         "rawType": "integer",
         "rawDescription": "The ID of a team to set as the parent team.",
         "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+        "name": "ldap_dn",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.0/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.0/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+        "childParamsGroups": []
       }
     ],
     "responses": [
@@ -33679,13 +33695,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -35518,13 +35535,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -59525,14 +59543,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -59611,14 +59629,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -59709,14 +59727,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -59795,14 +59813,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json
index 73b6635e84..71638a9512 100644
--- a/lib/rest/static/decorated/ghes-3.1.json
+++ b/lib/rest/static/decorated/ghes-3.1.json
@@ -25494,17 +25494,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -25515,6 +25514,15 @@
                 "rawType": "integer",
                 "rawDescription": "The ID of a team to set as the parent team.",
                 "childParamsGroups": []
+              },
+              "ldap_dn": {
+                "type": "string",
+                "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+                "name": "ldap_dn",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.1/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+                "childParamsGroups": []
               }
             },
             "required": [
@@ -25524,7 +25532,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -25600,17 +25608,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -25621,6 +25628,15 @@
         "rawType": "integer",
         "rawDescription": "The ID of a team to set as the parent team.",
         "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+        "name": "ldap_dn",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.1/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+        "childParamsGroups": []
       }
     ],
     "responses": [
@@ -33679,13 +33695,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -35518,13 +35535,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -60070,14 +60088,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -60156,14 +60174,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -60254,14 +60272,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -60340,14 +60358,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json
index 0efeb83a29..b471b6efe7 100644
--- a/lib/rest/static/decorated/ghes-3.2.json
+++ b/lib/rest/static/decorated/ghes-3.2.json
@@ -25997,17 +25997,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -26018,6 +26017,15 @@
                 "rawType": "integer",
                 "rawDescription": "The ID of a team to set as the parent team.",
                 "childParamsGroups": []
+              },
+              "ldap_dn": {
+                "type": "string",
+                "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+                "name": "ldap_dn",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.2/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+                "childParamsGroups": []
               }
             },
             "required": [
@@ -26027,7 +26035,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -26103,17 +26111,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -26124,6 +26131,15 @@
         "rawType": "integer",
         "rawDescription": "The ID of a team to set as the parent team.",
         "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+        "name": "ldap_dn",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.2/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+        "childParamsGroups": []
       }
     ],
     "responses": [
@@ -34591,13 +34607,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -36768,13 +36785,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -62249,14 +62267,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -62335,14 +62353,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -62433,14 +62451,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -62519,14 +62537,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json
index 1ab8643390..96bfec43e2 100644
--- a/lib/rest/static/decorated/ghes-3.3.json
+++ b/lib/rest/static/decorated/ghes-3.3.json
@@ -26107,17 +26107,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -26128,6 +26127,15 @@
                 "rawType": "integer",
                 "rawDescription": "The ID of a team to set as the parent team.",
                 "childParamsGroups": []
+              },
+              "ldap_dn": {
+                "type": "string",
+                "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+                "name": "ldap_dn",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.3/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+                "childParamsGroups": []
               }
             },
             "required": [
@@ -26137,7 +26145,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -26213,17 +26221,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -26234,6 +26241,15 @@
         "rawType": "integer",
         "rawDescription": "The ID of a team to set as the parent team.",
         "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>The <a href=\"https://www.ldap.com/ldap-dns-and-rdns\">distinguished name</a> (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team\">Update LDAP mapping for a team</a>\" endpoint to change the LDAP DN. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync\">Using LDAP</a>.\"</p>",
+        "name": "ldap_dn",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.3/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\"",
+        "childParamsGroups": []
       }
     ],
     "responses": [
@@ -34438,13 +34454,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -34849,220 +34866,6 @@
       }
     ]
   },
-  {
-    "verb": "get",
-    "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}",
-    "serverUrl": "http(s)://{hostname}/api/v3",
-    "parameters": [
-      {
-        "name": "owner",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "string"
-        },
-        "descriptionHTML": ""
-      },
-      {
-        "name": "repo",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "string"
-        },
-        "descriptionHTML": ""
-      },
-      {
-        "name": "run_id",
-        "description": "The id of the workflow run.",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": "<p>The id of the workflow run.</p>"
-      },
-      {
-        "name": "attempt_number",
-        "description": "The attempt number of the workflow run.",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": "<p>The attempt number of the workflow run.</p>"
-      },
-      {
-        "name": "exclude_pull_requests",
-        "description": "If `true` pull requests are omitted from the response (empty array).",
-        "in": "query",
-        "required": false,
-        "schema": {
-          "type": "boolean",
-          "default": false
-        },
-        "descriptionHTML": "<p>If <code>true</code> pull requests are omitted from the response (empty array).</p>"
-      }
-    ],
-    "x-codeSamples": [
-      {
-        "lang": "Shell",
-        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42",
-        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42</code></pre>"
-      },
-      {
-        "lang": "JavaScript",
-        "source": "await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  run_id: 42,\n  attempt_number: 42\n})",
-        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>,\n  <span class=\"hljs-attr\">run_id</span>: <span class=\"hljs-number\">42</span>,\n  <span class=\"hljs-attr\">attempt_number</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
-      }
-    ],
-    "summary": "Get a workflow run attempt",
-    "description": "Gets a specific workflow run attempt. Anyone with read access to the repository\ncan use this endpoint. If the repository is private you must use an access token\nwith the `repo` scope. GitHub Apps must have the `actions:read` permission to\nuse this endpoint.",
-    "tags": [
-      "actions"
-    ],
-    "operationId": "actions/get-workflow-run-attempt",
-    "externalDocs": {
-      "description": "API method documentation",
-      "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/actions#get-a-workflow-run-attempt"
-    },
-    "x-github": {
-      "githubCloudOnly": false,
-      "enabledForGitHubApps": true,
-      "category": "actions",
-      "subcategory": "workflow-runs"
-    },
-    "slug": "get-a-workflow-run-attempt",
-    "category": "actions",
-    "categoryLabel": "Actions",
-    "subcategory": "workflow-runs",
-    "subcategoryLabel": "Workflow runs",
-    "notes": [],
-    "bodyParameters": [],
-    "descriptionHTML": "<p>Gets a specific workflow run attempt. Anyone with read access to the repository\ncan use this endpoint. If the repository is private you must use an access token\nwith the <code>repo</code> scope. GitHub Apps must have the <code>actions:read</code> permission to\nuse this endpoint.</p>",
-    "responses": [
-      {
-        "httpStatusCode": "200",
-        "httpStatusMessage": "OK",
-        "description": "<p>Response</p>",
-        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">30433642</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Build\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"check_suite_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">42</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"check_suite_node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOkNoZWNrU3VpdGU0Mg==\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"head_branch\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"master\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"head_sha\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"acb5820ced9479c074f688cc328bf03f341a511d\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"run_number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">562</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"event\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"push\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"queued\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"workflow_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">159038</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octo-org/octo-repo/actions/runs/30433642\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"pull_requests\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span><span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-22T19:33:08Z\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-22T19:33:08Z\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"jobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/jobs\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"logs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/logs\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"check_suite_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/check-suites/414944374\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"artifacts_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/artifacts\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"cancel_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/cancel\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"rerun_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/rerun\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"workflow_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"head_commit\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n    <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"acb5820ced9479c074f688cc328bf03f341a511d\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"tree_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"d23f6eedb1e1b9610bbc754ddb5197bfe7271223\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"message\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Create linter.yaml\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"timestamp\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-22T19:33:05Z\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"author\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Octo Cat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"email\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat@github.com\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"committer\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"GitHub\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"email\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"noreply@github.com\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n    <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/events\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/forks\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/languages\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/merges\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/tags\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/teams\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"http://api.github.com/repos/octocat/Hello-World/hooks\"</span>\n  <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"head_repository\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n    <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">217723378</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkyMTc3MjMzNzg=\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octo-repo\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octo-org/octo-repo\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">true</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octo-org/octo-repo\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">null</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/forks\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/teams\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/hooks\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/events\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/tags\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/languages\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/merges\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/deployments\"</span>\n  <span class=\"hljs-punctuation\">}</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
-      }
-    ]
-  },
-  {
-    "verb": "get",
-    "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs",
-    "serverUrl": "http(s)://{hostname}/api/v3",
-    "parameters": [
-      {
-        "name": "owner",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "string"
-        },
-        "descriptionHTML": ""
-      },
-      {
-        "name": "repo",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "string"
-        },
-        "descriptionHTML": ""
-      },
-      {
-        "name": "run_id",
-        "description": "The id of the workflow run.",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": "<p>The id of the workflow run.</p>"
-      },
-      {
-        "name": "attempt_number",
-        "description": "The attempt number of the workflow run.",
-        "in": "path",
-        "required": true,
-        "schema": {
-          "type": "integer"
-        },
-        "descriptionHTML": "<p>The attempt number of the workflow run.</p>"
-      },
-      {
-        "name": "per_page",
-        "description": "Results per page (max 100)",
-        "in": "query",
-        "schema": {
-          "type": "integer",
-          "default": 30
-        },
-        "descriptionHTML": "<p>Results per page (max 100)</p>"
-      },
-      {
-        "name": "page",
-        "description": "Page number of the results to fetch.",
-        "in": "query",
-        "schema": {
-          "type": "integer",
-          "default": 1
-        },
-        "descriptionHTML": "<p>Page number of the results to fetch.</p>"
-      }
-    ],
-    "x-codeSamples": [
-      {
-        "lang": "Shell",
-        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs",
-        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  http(s)://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs</code></pre>"
-      },
-      {
-        "lang": "JavaScript",
-        "source": "await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  run_id: 42,\n  attempt_number: 42\n})",
-        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>,\n  <span class=\"hljs-attr\">run_id</span>: <span class=\"hljs-number\">42</span>,\n  <span class=\"hljs-attr\">attempt_number</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
-      }
-    ],
-    "summary": "List jobs for a workflow run attempt",
-    "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#parameters).",
-    "tags": [
-      "actions"
-    ],
-    "operationId": "actions/list-jobs-for-workflow-run-attempt",
-    "externalDocs": {
-      "description": "API method documentation",
-      "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/actions#list-jobs-for-a-workflow-run-attempt"
-    },
-    "x-github": {
-      "githubCloudOnly": false,
-      "enabledForGitHubApps": true,
-      "category": "actions",
-      "subcategory": "workflow-jobs"
-    },
-    "slug": "list-jobs-for-a-workflow-run-attempt",
-    "category": "actions",
-    "categoryLabel": "Actions",
-    "subcategory": "workflow-jobs",
-    "subcategoryLabel": "Workflow jobs",
-    "notes": [],
-    "bodyParameters": [],
-    "descriptionHTML": "<p>Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the <code>repo</code> scope. GitHub Apps must have the <code>actions:read</code> permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#parameters\">Parameters</a>.</p>",
-    "responses": [
-      {
-        "httpStatusCode": "200",
-        "httpStatusMessage": "OK",
-        "description": "<p>Response</p>",
-        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"total_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"jobs\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">399444496</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"run_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">29679449</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"run_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"head_sha\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octo-org/octo-repo/runs/399444496\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T17:42:40Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T17:44:39Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"build\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"steps\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Set up job\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:40.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:41.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Run actions/checkout@v2\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">2</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:41.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:45.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Set up Ruby\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">3</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:45.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:45.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Run actions/cache@v2\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">4</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:45.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:48.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Install Bundler\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">5</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:48.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:52.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Install Gems\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">6</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:52.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:53.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Run Tests\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">7</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:53.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:59.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Deploy to Heroku\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">8</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:42:59.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:44:39.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Post actions/cache@v2\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">16</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:44:39.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:44:39.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-punctuation\">{</span>\n          <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Complete job\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"status\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"completed\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"conclusion\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"success\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"number\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">17</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"started_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:44:39.000-08:00\"</span><span class=\"hljs-punctuation\">,</span>\n          <span class=\"hljs-attr\">\"completed_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-20T09:44:39.000-08:00\"</span>\n        <span class=\"hljs-punctuation\">}</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"check_run_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"labels\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n        <span class=\"hljs-string\">\"self-hosted\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"foo\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-string\">\"bar\"</span>\n      <span class=\"hljs-punctuation\">]</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"runner_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"runner_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"my runner\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"runner_group_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">2</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"runner_group_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"my runner group\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
-      },
-      {
-        "httpStatusCode": "404",
-        "httpStatusMessage": "Not Found",
-        "description": "<p>Resource not found</p>"
-      }
-    ]
-  },
   {
     "verb": "post",
     "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/cancel",
@@ -36829,13 +36632,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -62542,14 +62346,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -62628,14 +62432,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -62726,14 +62530,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -62812,14 +62616,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index 05270b4f39..939569c1c6 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -19008,17 +19008,16 @@
               },
               "permission": {
                 "type": "string",
-                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+                "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
                 "enum": [
                   "pull",
-                  "push",
-                  "admin"
+                  "push"
                 ],
                 "default": "pull",
                 "name": "permission",
                 "in": "body",
                 "rawType": "string",
-                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                 "childParamsGroups": []
               },
               "parent_team_id": {
@@ -19038,7 +19037,7 @@
           "example": {
             "name": "Justice League",
             "description": "A great team",
-            "permission": "admin",
+            "permission": "push",
             "privacy": "closed"
           }
         }
@@ -19114,17 +19113,16 @@
       },
       {
         "type": "string",
-        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.<br>\n* <code>admin</code> - team members can pull, push and administer newly-added repositories.</p>",
+        "description": "<p><strong>Deprecated</strong>. The permission that new repositories will be added to the team with when none is specified. Can be one of:<br>\n* <code>pull</code> - team members can pull, but not push to or administer newly-added repositories.<br>\n* <code>push</code> - team members can pull and push, but not administer newly-added repositories.</p>",
         "enum": [
           "pull",
-          "push",
-          "admin"
+          "push"
         ],
         "default": "pull",
         "name": "permission",
         "in": "body",
         "rawType": "string",
-        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+        "rawDescription": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
         "childParamsGroups": []
       },
       {
@@ -27246,13 +27244,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -29466,13 +29465,14 @@
       },
       {
         "name": "created",
+        "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
         "in": "query",
         "required": false,
         "schema": {
           "type": "string",
           "format": "date-time"
         },
-        "descriptionHTML": ""
+        "descriptionHTML": "<p>Returns workflow runs created within the given date-time range. For more information on the syntax, see \"<a href=\"https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates\">Understanding the search syntax</a>.\"</p>"
       },
       {
         "name": "exclude_pull_requests",
@@ -54768,14 +54768,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#set-labels-for-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -54854,14 +54854,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also replace all of the labels for an issue. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/rest/reference/issues#set-labels-for-an-issue\">Set labels for an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#set-labels-for-an-issue).\"",
         "childParamsGroups": []
       }
     ],
@@ -54952,14 +54952,14 @@
                   "labels": {
                     "type": "array of strings",
                     "minItems": 1,
-                    "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+                    "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
                     "items": {
                       "type": "string"
                     },
                     "name": "labels",
                     "in": "body",
                     "rawType": "array",
-                    "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                    "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#add-labels-to-an-issue).\"",
                     "childParamsGroups": []
                   }
                 }
@@ -55038,14 +55038,14 @@
       {
         "type": "array of strings",
         "minItems": 1,
-        "description": "<p>The names of the labels to add to the issue. You can pass an empty array to remove all labels. <strong>Note:</strong> Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key.</p>",
+        "description": "<p>The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a <code>string</code> or an <code>array</code> of labels directly, but GitHub recommends passing an object with the <code>labels</code> key. You can also add labels to the existing labels for an issue. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/rest/reference/issues#add-labels-to-an-issue\">Add labels to an issue</a>.\"</p>",
         "items": {
           "type": "string"
         },
         "name": "labels",
         "in": "body",
         "rawType": "array",
-        "rawDescription": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+        "rawDescription": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#add-labels-to-an-issue).\"",
         "childParamsGroups": []
       }
     ],
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index dd30b1b6b3..2de5b76484 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -66686,7 +66686,7 @@
     "/orgs/{org}/audit-log": {
       "get": {
         "summary": "Get the audit log for an organization",
-        "description": "Gets the audit log for an organization. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization).\"\n\nTo use this endpoint, you must be an organization owner, and you must use an access token with the `admin:org` scope. GitHub Apps must have the `organization_administration` read permission to use this endpoint.",
+        "description": "Gets the audit log for an organization. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization).\"\n\nThis endpoint is available for organizations on GitHub Enterprise Cloud. To use this endpoint, you must be an organization owner, and you must use an access token with the `admin:org` scope. GitHub Apps must have the `organization_administration` read permission to use this endpoint.",
         "operationId": "orgs/get-audit-log",
         "tags": [
           "orgs"
@@ -67407,6 +67407,2814 @@
         }
       }
     },
+    "/orgs/{org}/code-scanning/alerts": {
+      "get": {
+        "summary": "List code scanning alerts for an organization",
+        "description": "Lists all code scanning alerts for the default branch (usually `main`\nor `master`) for all eligible repositories in an organization.\nTo use this endpoint, you must be an administrator for the repository or organization, and you must use an access token with the `repo` scope or `security_events` scope.\n\nGitHub Apps must have the `code_scanning_alerts` read permission to use this endpoint.",
+        "tags": [
+          "code-scanning"
+        ],
+        "operationId": "code-scanning/list-alerts-for-org",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/code-scanning#list-code-scanning-alerts-by-organization"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "before",
+            "description": "A cursor, as given in the [Link header](https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events before this cursor.",
+            "in": "query",
+            "required": false,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "after",
+            "description": "A cursor, as given in the [Link header](https://docs.github.com/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events after this cursor.",
+            "in": "query",
+            "required": false,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "page",
+            "description": "Page number of the results to fetch.",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 1
+            }
+          },
+          {
+            "name": "per_page",
+            "description": "Results per page (max 100)",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 30
+            }
+          },
+          {
+            "name": "direction",
+            "description": "One of `asc` (ascending) or `desc` (descending).",
+            "in": "query",
+            "required": false,
+            "schema": {
+              "type": "string",
+              "enum": [
+                "asc",
+                "desc"
+              ],
+              "default": "desc"
+            }
+          },
+          {
+            "name": "state",
+            "description": "Set to `open`, `fixed`, or `dismissed` to list code scanning alerts in a specific state.",
+            "in": "query",
+            "required": false,
+            "schema": {
+              "type": "string",
+              "description": "State of a code scanning alert.",
+              "enum": [
+                "open",
+                "closed",
+                "dismissed",
+                "fixed"
+              ]
+            }
+          },
+          {
+            "name": "sort",
+            "description": "Can be one of `created`, `updated`.",
+            "in": "query",
+            "required": false,
+            "schema": {
+              "type": "string",
+              "enum": [
+                "created",
+                "updated"
+              ],
+              "default": "created"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "number": {
+                        "type": "integer",
+                        "description": "The security alert number.",
+                        "readOnly": true
+                      },
+                      "created_at": {
+                        "type": "string",
+                        "description": "The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.",
+                        "format": "date-time",
+                        "readOnly": true
+                      },
+                      "updated_at": {
+                        "type": "string",
+                        "description": "The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.",
+                        "format": "date-time",
+                        "readOnly": true
+                      },
+                      "url": {
+                        "type": "string",
+                        "description": "The REST API URL of the alert resource.",
+                        "format": "uri",
+                        "readOnly": true
+                      },
+                      "html_url": {
+                        "type": "string",
+                        "description": "The GitHub URL of the alert resource.",
+                        "format": "uri",
+                        "readOnly": true
+                      },
+                      "instances_url": {
+                        "type": "string",
+                        "description": "The REST API URL for fetching the list of instances for an alert.",
+                        "format": "uri",
+                        "readOnly": true
+                      },
+                      "state": {
+                        "type": "string",
+                        "description": "State of a code scanning alert.",
+                        "enum": [
+                          "open",
+                          "closed",
+                          "dismissed",
+                          "fixed"
+                        ]
+                      },
+                      "fixed_at": {
+                        "type": "string",
+                        "description": "The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.",
+                        "format": "date-time",
+                        "readOnly": true,
+                        "nullable": true
+                      },
+                      "dismissed_by": {
+                        "title": "Simple User",
+                        "description": "Simple User",
+                        "type": "object",
+                        "properties": {
+                          "name": {
+                            "nullable": true,
+                            "type": "string"
+                          },
+                          "email": {
+                            "nullable": true,
+                            "type": "string"
+                          },
+                          "login": {
+                            "type": "string",
+                            "example": "octocat"
+                          },
+                          "id": {
+                            "type": "integer",
+                            "example": 1
+                          },
+                          "node_id": {
+                            "type": "string",
+                            "example": "MDQ6VXNlcjE="
+                          },
+                          "avatar_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://github.com/images/error/octocat_happy.gif"
+                          },
+                          "gravatar_id": {
+                            "type": "string",
+                            "example": "41d064eb2195891e12d0413f63227ea7",
+                            "nullable": true
+                          },
+                          "url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat"
+                          },
+                          "html_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://github.com/octocat"
+                          },
+                          "followers_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat/followers"
+                          },
+                          "following_url": {
+                            "type": "string",
+                            "example": "https://api.github.com/users/octocat/following{/other_user}"
+                          },
+                          "gists_url": {
+                            "type": "string",
+                            "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                          },
+                          "starred_url": {
+                            "type": "string",
+                            "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                          },
+                          "subscriptions_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat/subscriptions"
+                          },
+                          "organizations_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat/orgs"
+                          },
+                          "repos_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat/repos"
+                          },
+                          "events_url": {
+                            "type": "string",
+                            "example": "https://api.github.com/users/octocat/events{/privacy}"
+                          },
+                          "received_events_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/users/octocat/received_events"
+                          },
+                          "type": {
+                            "type": "string",
+                            "example": "User"
+                          },
+                          "site_admin": {
+                            "type": "boolean"
+                          },
+                          "starred_at": {
+                            "type": "string",
+                            "example": "\"2020-07-09T00:17:55Z\""
+                          }
+                        },
+                        "required": [
+                          "avatar_url",
+                          "events_url",
+                          "followers_url",
+                          "following_url",
+                          "gists_url",
+                          "gravatar_id",
+                          "html_url",
+                          "id",
+                          "node_id",
+                          "login",
+                          "organizations_url",
+                          "received_events_url",
+                          "repos_url",
+                          "site_admin",
+                          "starred_url",
+                          "subscriptions_url",
+                          "type",
+                          "url"
+                        ],
+                        "nullable": true
+                      },
+                      "dismissed_at": {
+                        "type": "string",
+                        "description": "The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.",
+                        "format": "date-time",
+                        "readOnly": true,
+                        "nullable": true
+                      },
+                      "dismissed_reason": {
+                        "type": "string",
+                        "description": "**Required when the state is dismissed.** The reason for dismissing or closing the alert. Can be one of: `false positive`, `won't fix`, and `used in tests`.",
+                        "nullable": true,
+                        "enum": [
+                          null,
+                          "false positive",
+                          "won't fix",
+                          "used in tests"
+                        ]
+                      },
+                      "rule": {
+                        "type": "object",
+                        "properties": {
+                          "id": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "A unique identifier for the rule used to detect the alert."
+                          },
+                          "name": {
+                            "type": "string",
+                            "description": "The name of the rule used to detect the alert."
+                          },
+                          "severity": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "The severity of the alert.",
+                            "enum": [
+                              "none",
+                              "note",
+                              "warning",
+                              "error"
+                            ]
+                          },
+                          "security_severity_level": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "The security severity of the alert.",
+                            "enum": [
+                              "low",
+                              "medium",
+                              "high",
+                              "critical"
+                            ]
+                          },
+                          "description": {
+                            "type": "string",
+                            "description": "A short description of the rule used to detect the alert."
+                          },
+                          "full_description": {
+                            "type": "string",
+                            "description": "description of the rule used to detect the alert."
+                          },
+                          "tags": {
+                            "nullable": true,
+                            "type": "array",
+                            "description": "A set of tags applicable for the rule.",
+                            "items": {
+                              "type": "string"
+                            }
+                          },
+                          "help": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "Detailed documentation for the rule as GitHub Flavored Markdown."
+                          }
+                        }
+                      },
+                      "tool": {
+                        "type": "object",
+                        "properties": {
+                          "name": {
+                            "type": "string",
+                            "description": "The name of the tool used to generate the code scanning analysis."
+                          },
+                          "version": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "The version of the tool used to generate the code scanning analysis."
+                          },
+                          "guid": {
+                            "nullable": true,
+                            "type": "string",
+                            "description": "The GUID of the tool used to generate the code scanning analysis, if provided in the uploaded SARIF data."
+                          }
+                        }
+                      },
+                      "most_recent_instance": {
+                        "type": "object",
+                        "properties": {
+                          "ref": {
+                            "type": "string",
+                            "description": "The full Git reference, formatted as `refs/heads/<branch name>`,\n`refs/pull/<number>/merge`, or `refs/pull/<number>/head`."
+                          },
+                          "analysis_key": {
+                            "type": "string",
+                            "description": "Identifies the configuration under which the analysis was executed. For example, in GitHub Actions this includes the workflow filename and job name."
+                          },
+                          "environment": {
+                            "type": "string",
+                            "description": "Identifies the variable values associated with the environment in which the analysis that generated this alert instance was performed, such as the language that was analyzed."
+                          },
+                          "category": {
+                            "type": "string",
+                            "description": "Identifies the configuration under which the analysis was executed. Used to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code."
+                          },
+                          "state": {
+                            "type": "string",
+                            "description": "State of a code scanning alert.",
+                            "enum": [
+                              "open",
+                              "closed",
+                              "dismissed",
+                              "fixed"
+                            ]
+                          },
+                          "commit_sha": {
+                            "type": "string"
+                          },
+                          "message": {
+                            "type": "object",
+                            "properties": {
+                              "text": {
+                                "type": "string"
+                              }
+                            }
+                          },
+                          "location": {
+                            "type": "object",
+                            "description": "Describe a region within a file for the alert.",
+                            "properties": {
+                              "path": {
+                                "type": "string"
+                              },
+                              "start_line": {
+                                "type": "integer"
+                              },
+                              "end_line": {
+                                "type": "integer"
+                              },
+                              "start_column": {
+                                "type": "integer"
+                              },
+                              "end_column": {
+                                "type": "integer"
+                              }
+                            }
+                          },
+                          "html_url": {
+                            "type": "string"
+                          },
+                          "classifications": {
+                            "type": "array",
+                            "description": "Classifications that have been applied to the file that triggered the alert.\nFor example identifying it as documentation, or a generated file.",
+                            "items": {
+                              "type": "string",
+                              "description": "A classification of the file. For example to identify it as generated.",
+                              "nullable": true,
+                              "enum": [
+                                "source",
+                                "generated",
+                                "test",
+                                "library"
+                              ]
+                            }
+                          }
+                        }
+                      },
+                      "repository": {
+                        "title": "Minimal Repository",
+                        "description": "Minimal Repository",
+                        "type": "object",
+                        "properties": {
+                          "id": {
+                            "type": "integer",
+                            "example": 1296269
+                          },
+                          "node_id": {
+                            "type": "string",
+                            "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
+                          },
+                          "name": {
+                            "type": "string",
+                            "example": "Hello-World"
+                          },
+                          "full_name": {
+                            "type": "string",
+                            "example": "octocat/Hello-World"
+                          },
+                          "owner": {
+                            "title": "Simple User",
+                            "description": "Simple User",
+                            "type": "object",
+                            "properties": {
+                              "name": {
+                                "nullable": true,
+                                "type": "string"
+                              },
+                              "email": {
+                                "nullable": true,
+                                "type": "string"
+                              },
+                              "login": {
+                                "type": "string",
+                                "example": "octocat"
+                              },
+                              "id": {
+                                "type": "integer",
+                                "example": 1
+                              },
+                              "node_id": {
+                                "type": "string",
+                                "example": "MDQ6VXNlcjE="
+                              },
+                              "avatar_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/images/error/octocat_happy.gif"
+                              },
+                              "gravatar_id": {
+                                "type": "string",
+                                "example": "41d064eb2195891e12d0413f63227ea7",
+                                "nullable": true
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/octocat"
+                              },
+                              "followers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/followers"
+                              },
+                              "following_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/following{/other_user}"
+                              },
+                              "gists_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                              },
+                              "starred_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                              },
+                              "subscriptions_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/subscriptions"
+                              },
+                              "organizations_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/orgs"
+                              },
+                              "repos_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/repos"
+                              },
+                              "events_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/events{/privacy}"
+                              },
+                              "received_events_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/received_events"
+                              },
+                              "type": {
+                                "type": "string",
+                                "example": "User"
+                              },
+                              "site_admin": {
+                                "type": "boolean"
+                              },
+                              "starred_at": {
+                                "type": "string",
+                                "example": "\"2020-07-09T00:17:55Z\""
+                              }
+                            },
+                            "required": [
+                              "avatar_url",
+                              "events_url",
+                              "followers_url",
+                              "following_url",
+                              "gists_url",
+                              "gravatar_id",
+                              "html_url",
+                              "id",
+                              "node_id",
+                              "login",
+                              "organizations_url",
+                              "received_events_url",
+                              "repos_url",
+                              "site_admin",
+                              "starred_url",
+                              "subscriptions_url",
+                              "type",
+                              "url"
+                            ]
+                          },
+                          "private": {
+                            "type": "boolean"
+                          },
+                          "html_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://github.com/octocat/Hello-World"
+                          },
+                          "description": {
+                            "type": "string",
+                            "example": "This your first repo!",
+                            "nullable": true
+                          },
+                          "fork": {
+                            "type": "boolean"
+                          },
+                          "url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/repos/octocat/Hello-World"
+                          },
+                          "archive_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
+                          },
+                          "assignees_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
+                          },
+                          "blobs_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
+                          },
+                          "branches_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
+                          },
+                          "collaborators_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
+                          },
+                          "comments_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
+                          },
+                          "commits_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
+                          },
+                          "compare_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
+                          },
+                          "contents_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
+                          },
+                          "contributors_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
+                          },
+                          "deployments_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
+                          },
+                          "downloads_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
+                          },
+                          "events_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/events"
+                          },
+                          "forks_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/forks"
+                          },
+                          "git_commits_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
+                          },
+                          "git_refs_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
+                          },
+                          "git_tags_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
+                          },
+                          "git_url": {
+                            "type": "string"
+                          },
+                          "issue_comment_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
+                          },
+                          "issue_events_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
+                          },
+                          "issues_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
+                          },
+                          "keys_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
+                          },
+                          "labels_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
+                          },
+                          "languages_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/languages"
+                          },
+                          "merges_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/merges"
+                          },
+                          "milestones_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
+                          },
+                          "notifications_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
+                          },
+                          "pulls_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
+                          },
+                          "releases_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
+                          },
+                          "ssh_url": {
+                            "type": "string"
+                          },
+                          "stargazers_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
+                          },
+                          "statuses_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
+                          },
+                          "subscribers_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
+                          },
+                          "subscription_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
+                          },
+                          "tags_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/tags"
+                          },
+                          "teams_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/teams"
+                          },
+                          "trees_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
+                          },
+                          "clone_url": {
+                            "type": "string"
+                          },
+                          "mirror_url": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "hooks_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
+                          },
+                          "svn_url": {
+                            "type": "string"
+                          },
+                          "homepage": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "language": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "forks_count": {
+                            "type": "integer"
+                          },
+                          "stargazers_count": {
+                            "type": "integer"
+                          },
+                          "watchers_count": {
+                            "type": "integer"
+                          },
+                          "size": {
+                            "type": "integer"
+                          },
+                          "default_branch": {
+                            "type": "string"
+                          },
+                          "open_issues_count": {
+                            "type": "integer"
+                          },
+                          "is_template": {
+                            "type": "boolean"
+                          },
+                          "topics": {
+                            "type": "array",
+                            "items": {
+                              "type": "string"
+                            }
+                          },
+                          "has_issues": {
+                            "type": "boolean"
+                          },
+                          "has_projects": {
+                            "type": "boolean"
+                          },
+                          "has_wiki": {
+                            "type": "boolean"
+                          },
+                          "has_pages": {
+                            "type": "boolean"
+                          },
+                          "has_downloads": {
+                            "type": "boolean"
+                          },
+                          "archived": {
+                            "type": "boolean"
+                          },
+                          "disabled": {
+                            "type": "boolean"
+                          },
+                          "visibility": {
+                            "type": "string"
+                          },
+                          "pushed_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:06:43Z",
+                            "nullable": true
+                          },
+                          "created_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:01:12Z",
+                            "nullable": true
+                          },
+                          "updated_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:14:43Z",
+                            "nullable": true
+                          },
+                          "permissions": {
+                            "type": "object",
+                            "properties": {
+                              "admin": {
+                                "type": "boolean"
+                              },
+                              "maintain": {
+                                "type": "boolean"
+                              },
+                              "push": {
+                                "type": "boolean"
+                              },
+                              "triage": {
+                                "type": "boolean"
+                              },
+                              "pull": {
+                                "type": "boolean"
+                              }
+                            }
+                          },
+                          "role_name": {
+                            "type": "string",
+                            "example": "admin"
+                          },
+                          "template_repository": {
+                            "title": "Repository",
+                            "description": "A git repository",
+                            "type": "object",
+                            "properties": {
+                              "id": {
+                                "description": "Unique identifier of the repository",
+                                "example": 42,
+                                "type": "integer"
+                              },
+                              "node_id": {
+                                "type": "string",
+                                "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
+                              },
+                              "name": {
+                                "description": "The name of the repository.",
+                                "type": "string",
+                                "example": "Team Environment"
+                              },
+                              "full_name": {
+                                "type": "string",
+                                "example": "octocat/Hello-World"
+                              },
+                              "license": {
+                                "title": "License Simple",
+                                "description": "License Simple",
+                                "type": "object",
+                                "properties": {
+                                  "key": {
+                                    "type": "string",
+                                    "example": "mit"
+                                  },
+                                  "name": {
+                                    "type": "string",
+                                    "example": "MIT License"
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "nullable": true,
+                                    "format": "uri",
+                                    "example": "https://api.github.com/licenses/mit"
+                                  },
+                                  "spdx_id": {
+                                    "type": "string",
+                                    "nullable": true,
+                                    "example": "MIT"
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDc6TGljZW5zZW1pdA=="
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri"
+                                  }
+                                },
+                                "required": [
+                                  "key",
+                                  "name",
+                                  "url",
+                                  "spdx_id",
+                                  "node_id"
+                                ],
+                                "nullable": true
+                              },
+                              "organization": {
+                                "title": "Simple User",
+                                "description": "Simple User",
+                                "type": "object",
+                                "properties": {
+                                  "name": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "email": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "login": {
+                                    "type": "string",
+                                    "example": "octocat"
+                                  },
+                                  "id": {
+                                    "type": "integer",
+                                    "example": 1
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDQ6VXNlcjE="
+                                  },
+                                  "avatar_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/images/error/octocat_happy.gif"
+                                  },
+                                  "gravatar_id": {
+                                    "type": "string",
+                                    "example": "41d064eb2195891e12d0413f63227ea7",
+                                    "nullable": true
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat"
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/octocat"
+                                  },
+                                  "followers_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/followers"
+                                  },
+                                  "following_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/following{/other_user}"
+                                  },
+                                  "gists_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                                  },
+                                  "starred_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                                  },
+                                  "subscriptions_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/subscriptions"
+                                  },
+                                  "organizations_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/orgs"
+                                  },
+                                  "repos_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/repos"
+                                  },
+                                  "events_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/events{/privacy}"
+                                  },
+                                  "received_events_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/received_events"
+                                  },
+                                  "type": {
+                                    "type": "string",
+                                    "example": "User"
+                                  },
+                                  "site_admin": {
+                                    "type": "boolean"
+                                  },
+                                  "starred_at": {
+                                    "type": "string",
+                                    "example": "\"2020-07-09T00:17:55Z\""
+                                  }
+                                },
+                                "required": [
+                                  "avatar_url",
+                                  "events_url",
+                                  "followers_url",
+                                  "following_url",
+                                  "gists_url",
+                                  "gravatar_id",
+                                  "html_url",
+                                  "id",
+                                  "node_id",
+                                  "login",
+                                  "organizations_url",
+                                  "received_events_url",
+                                  "repos_url",
+                                  "site_admin",
+                                  "starred_url",
+                                  "subscriptions_url",
+                                  "type",
+                                  "url"
+                                ],
+                                "nullable": true
+                              },
+                              "forks": {
+                                "type": "integer"
+                              },
+                              "permissions": {
+                                "type": "object",
+                                "properties": {
+                                  "admin": {
+                                    "type": "boolean"
+                                  },
+                                  "pull": {
+                                    "type": "boolean"
+                                  },
+                                  "triage": {
+                                    "type": "boolean"
+                                  },
+                                  "push": {
+                                    "type": "boolean"
+                                  },
+                                  "maintain": {
+                                    "type": "boolean"
+                                  }
+                                },
+                                "required": [
+                                  "admin",
+                                  "pull",
+                                  "push"
+                                ]
+                              },
+                              "owner": {
+                                "title": "Simple User",
+                                "description": "Simple User",
+                                "type": "object",
+                                "properties": {
+                                  "name": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "email": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "login": {
+                                    "type": "string",
+                                    "example": "octocat"
+                                  },
+                                  "id": {
+                                    "type": "integer",
+                                    "example": 1
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDQ6VXNlcjE="
+                                  },
+                                  "avatar_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/images/error/octocat_happy.gif"
+                                  },
+                                  "gravatar_id": {
+                                    "type": "string",
+                                    "example": "41d064eb2195891e12d0413f63227ea7",
+                                    "nullable": true
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat"
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/octocat"
+                                  },
+                                  "followers_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/followers"
+                                  },
+                                  "following_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/following{/other_user}"
+                                  },
+                                  "gists_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                                  },
+                                  "starred_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                                  },
+                                  "subscriptions_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/subscriptions"
+                                  },
+                                  "organizations_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/orgs"
+                                  },
+                                  "repos_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/repos"
+                                  },
+                                  "events_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/events{/privacy}"
+                                  },
+                                  "received_events_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/received_events"
+                                  },
+                                  "type": {
+                                    "type": "string",
+                                    "example": "User"
+                                  },
+                                  "site_admin": {
+                                    "type": "boolean"
+                                  },
+                                  "starred_at": {
+                                    "type": "string",
+                                    "example": "\"2020-07-09T00:17:55Z\""
+                                  }
+                                },
+                                "required": [
+                                  "avatar_url",
+                                  "events_url",
+                                  "followers_url",
+                                  "following_url",
+                                  "gists_url",
+                                  "gravatar_id",
+                                  "html_url",
+                                  "id",
+                                  "node_id",
+                                  "login",
+                                  "organizations_url",
+                                  "received_events_url",
+                                  "repos_url",
+                                  "site_admin",
+                                  "starred_url",
+                                  "subscriptions_url",
+                                  "type",
+                                  "url"
+                                ]
+                              },
+                              "private": {
+                                "description": "Whether the repository is private or public.",
+                                "default": false,
+                                "type": "boolean"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/octocat/Hello-World"
+                              },
+                              "description": {
+                                "type": "string",
+                                "example": "This your first repo!",
+                                "nullable": true
+                              },
+                              "fork": {
+                                "type": "boolean"
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/repos/octocat/Hello-World"
+                              },
+                              "archive_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
+                              },
+                              "assignees_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
+                              },
+                              "blobs_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
+                              },
+                              "branches_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
+                              },
+                              "collaborators_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
+                              },
+                              "comments_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
+                              },
+                              "commits_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
+                              },
+                              "compare_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
+                              },
+                              "contents_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
+                              },
+                              "contributors_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
+                              },
+                              "deployments_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
+                              },
+                              "downloads_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
+                              },
+                              "events_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/events"
+                              },
+                              "forks_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/forks"
+                              },
+                              "git_commits_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
+                              },
+                              "git_refs_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
+                              },
+                              "git_tags_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
+                              },
+                              "git_url": {
+                                "type": "string",
+                                "example": "git:github.com/octocat/Hello-World.git"
+                              },
+                              "issue_comment_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
+                              },
+                              "issue_events_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
+                              },
+                              "issues_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
+                              },
+                              "keys_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
+                              },
+                              "labels_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
+                              },
+                              "languages_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/languages"
+                              },
+                              "merges_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/merges"
+                              },
+                              "milestones_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
+                              },
+                              "notifications_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
+                              },
+                              "pulls_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
+                              },
+                              "releases_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
+                              },
+                              "ssh_url": {
+                                "type": "string",
+                                "example": "git@github.com:octocat/Hello-World.git"
+                              },
+                              "stargazers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
+                              },
+                              "statuses_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
+                              },
+                              "subscribers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
+                              },
+                              "subscription_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
+                              },
+                              "tags_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/tags"
+                              },
+                              "teams_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/teams"
+                              },
+                              "trees_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
+                              },
+                              "clone_url": {
+                                "type": "string",
+                                "example": "https://github.com/octocat/Hello-World.git"
+                              },
+                              "mirror_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "git:git.example.com/octocat/Hello-World",
+                                "nullable": true
+                              },
+                              "hooks_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
+                              },
+                              "svn_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://svn.github.com/octocat/Hello-World"
+                              },
+                              "homepage": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com",
+                                "nullable": true
+                              },
+                              "language": {
+                                "type": "string",
+                                "nullable": true
+                              },
+                              "forks_count": {
+                                "type": "integer",
+                                "example": 9
+                              },
+                              "stargazers_count": {
+                                "type": "integer",
+                                "example": 80
+                              },
+                              "watchers_count": {
+                                "type": "integer",
+                                "example": 80
+                              },
+                              "size": {
+                                "type": "integer",
+                                "example": 108
+                              },
+                              "default_branch": {
+                                "description": "The default branch of the repository.",
+                                "type": "string",
+                                "example": "master"
+                              },
+                              "open_issues_count": {
+                                "type": "integer",
+                                "example": 0
+                              },
+                              "is_template": {
+                                "description": "Whether this repository acts as a template that can be used to generate new repositories.",
+                                "default": false,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "topics": {
+                                "type": "array",
+                                "items": {
+                                  "type": "string"
+                                }
+                              },
+                              "has_issues": {
+                                "description": "Whether issues are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_projects": {
+                                "description": "Whether projects are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_wiki": {
+                                "description": "Whether the wiki is enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_pages": {
+                                "type": "boolean"
+                              },
+                              "has_downloads": {
+                                "description": "Whether downloads are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "archived": {
+                                "description": "Whether the repository is archived.",
+                                "default": false,
+                                "type": "boolean"
+                              },
+                              "disabled": {
+                                "type": "boolean",
+                                "description": "Returns whether or not this repository disabled."
+                              },
+                              "visibility": {
+                                "description": "The repository visibility: public, private, or internal.",
+                                "default": "public",
+                                "type": "string"
+                              },
+                              "pushed_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:06:43Z",
+                                "nullable": true
+                              },
+                              "created_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:01:12Z",
+                                "nullable": true
+                              },
+                              "updated_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:14:43Z",
+                                "nullable": true
+                              },
+                              "allow_rebase_merge": {
+                                "description": "Whether to allow rebase merges for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "template_repository": {
+                                "nullable": true,
+                                "type": "object",
+                                "properties": {
+                                  "id": {
+                                    "type": "integer"
+                                  },
+                                  "node_id": {
+                                    "type": "string"
+                                  },
+                                  "name": {
+                                    "type": "string"
+                                  },
+                                  "full_name": {
+                                    "type": "string"
+                                  },
+                                  "owner": {
+                                    "type": "object",
+                                    "properties": {
+                                      "login": {
+                                        "type": "string"
+                                      },
+                                      "id": {
+                                        "type": "integer"
+                                      },
+                                      "node_id": {
+                                        "type": "string"
+                                      },
+                                      "avatar_url": {
+                                        "type": "string"
+                                      },
+                                      "gravatar_id": {
+                                        "type": "string"
+                                      },
+                                      "url": {
+                                        "type": "string"
+                                      },
+                                      "html_url": {
+                                        "type": "string"
+                                      },
+                                      "followers_url": {
+                                        "type": "string"
+                                      },
+                                      "following_url": {
+                                        "type": "string"
+                                      },
+                                      "gists_url": {
+                                        "type": "string"
+                                      },
+                                      "starred_url": {
+                                        "type": "string"
+                                      },
+                                      "subscriptions_url": {
+                                        "type": "string"
+                                      },
+                                      "organizations_url": {
+                                        "type": "string"
+                                      },
+                                      "repos_url": {
+                                        "type": "string"
+                                      },
+                                      "events_url": {
+                                        "type": "string"
+                                      },
+                                      "received_events_url": {
+                                        "type": "string"
+                                      },
+                                      "type": {
+                                        "type": "string"
+                                      },
+                                      "site_admin": {
+                                        "type": "boolean"
+                                      }
+                                    }
+                                  },
+                                  "private": {
+                                    "type": "boolean"
+                                  },
+                                  "html_url": {
+                                    "type": "string"
+                                  },
+                                  "description": {
+                                    "type": "string"
+                                  },
+                                  "fork": {
+                                    "type": "boolean"
+                                  },
+                                  "url": {
+                                    "type": "string"
+                                  },
+                                  "archive_url": {
+                                    "type": "string"
+                                  },
+                                  "assignees_url": {
+                                    "type": "string"
+                                  },
+                                  "blobs_url": {
+                                    "type": "string"
+                                  },
+                                  "branches_url": {
+                                    "type": "string"
+                                  },
+                                  "collaborators_url": {
+                                    "type": "string"
+                                  },
+                                  "comments_url": {
+                                    "type": "string"
+                                  },
+                                  "commits_url": {
+                                    "type": "string"
+                                  },
+                                  "compare_url": {
+                                    "type": "string"
+                                  },
+                                  "contents_url": {
+                                    "type": "string"
+                                  },
+                                  "contributors_url": {
+                                    "type": "string"
+                                  },
+                                  "deployments_url": {
+                                    "type": "string"
+                                  },
+                                  "downloads_url": {
+                                    "type": "string"
+                                  },
+                                  "events_url": {
+                                    "type": "string"
+                                  },
+                                  "forks_url": {
+                                    "type": "string"
+                                  },
+                                  "git_commits_url": {
+                                    "type": "string"
+                                  },
+                                  "git_refs_url": {
+                                    "type": "string"
+                                  },
+                                  "git_tags_url": {
+                                    "type": "string"
+                                  },
+                                  "git_url": {
+                                    "type": "string"
+                                  },
+                                  "issue_comment_url": {
+                                    "type": "string"
+                                  },
+                                  "issue_events_url": {
+                                    "type": "string"
+                                  },
+                                  "issues_url": {
+                                    "type": "string"
+                                  },
+                                  "keys_url": {
+                                    "type": "string"
+                                  },
+                                  "labels_url": {
+                                    "type": "string"
+                                  },
+                                  "languages_url": {
+                                    "type": "string"
+                                  },
+                                  "merges_url": {
+                                    "type": "string"
+                                  },
+                                  "milestones_url": {
+                                    "type": "string"
+                                  },
+                                  "notifications_url": {
+                                    "type": "string"
+                                  },
+                                  "pulls_url": {
+                                    "type": "string"
+                                  },
+                                  "releases_url": {
+                                    "type": "string"
+                                  },
+                                  "ssh_url": {
+                                    "type": "string"
+                                  },
+                                  "stargazers_url": {
+                                    "type": "string"
+                                  },
+                                  "statuses_url": {
+                                    "type": "string"
+                                  },
+                                  "subscribers_url": {
+                                    "type": "string"
+                                  },
+                                  "subscription_url": {
+                                    "type": "string"
+                                  },
+                                  "tags_url": {
+                                    "type": "string"
+                                  },
+                                  "teams_url": {
+                                    "type": "string"
+                                  },
+                                  "trees_url": {
+                                    "type": "string"
+                                  },
+                                  "clone_url": {
+                                    "type": "string"
+                                  },
+                                  "mirror_url": {
+                                    "type": "string"
+                                  },
+                                  "hooks_url": {
+                                    "type": "string"
+                                  },
+                                  "svn_url": {
+                                    "type": "string"
+                                  },
+                                  "homepage": {
+                                    "type": "string"
+                                  },
+                                  "language": {
+                                    "type": "string"
+                                  },
+                                  "forks_count": {
+                                    "type": "integer"
+                                  },
+                                  "stargazers_count": {
+                                    "type": "integer"
+                                  },
+                                  "watchers_count": {
+                                    "type": "integer"
+                                  },
+                                  "size": {
+                                    "type": "integer"
+                                  },
+                                  "default_branch": {
+                                    "type": "string"
+                                  },
+                                  "open_issues_count": {
+                                    "type": "integer"
+                                  },
+                                  "is_template": {
+                                    "type": "boolean"
+                                  },
+                                  "topics": {
+                                    "type": "array",
+                                    "items": {
+                                      "type": "string"
+                                    }
+                                  },
+                                  "has_issues": {
+                                    "type": "boolean"
+                                  },
+                                  "has_projects": {
+                                    "type": "boolean"
+                                  },
+                                  "has_wiki": {
+                                    "type": "boolean"
+                                  },
+                                  "has_pages": {
+                                    "type": "boolean"
+                                  },
+                                  "has_downloads": {
+                                    "type": "boolean"
+                                  },
+                                  "archived": {
+                                    "type": "boolean"
+                                  },
+                                  "disabled": {
+                                    "type": "boolean"
+                                  },
+                                  "visibility": {
+                                    "type": "string"
+                                  },
+                                  "pushed_at": {
+                                    "type": "string"
+                                  },
+                                  "created_at": {
+                                    "type": "string"
+                                  },
+                                  "updated_at": {
+                                    "type": "string"
+                                  },
+                                  "permissions": {
+                                    "type": "object",
+                                    "properties": {
+                                      "admin": {
+                                        "type": "boolean"
+                                      },
+                                      "maintain": {
+                                        "type": "boolean"
+                                      },
+                                      "push": {
+                                        "type": "boolean"
+                                      },
+                                      "triage": {
+                                        "type": "boolean"
+                                      },
+                                      "pull": {
+                                        "type": "boolean"
+                                      }
+                                    }
+                                  },
+                                  "allow_rebase_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "temp_clone_token": {
+                                    "type": "string"
+                                  },
+                                  "allow_squash_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_auto_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "delete_branch_on_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_update_branch": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_merge_commit": {
+                                    "type": "boolean"
+                                  },
+                                  "subscribers_count": {
+                                    "type": "integer"
+                                  },
+                                  "network_count": {
+                                    "type": "integer"
+                                  }
+                                }
+                              },
+                              "temp_clone_token": {
+                                "type": "string"
+                              },
+                              "allow_squash_merge": {
+                                "description": "Whether to allow squash merges for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "allow_auto_merge": {
+                                "description": "Whether to allow Auto-merge to be used on pull requests.",
+                                "default": false,
+                                "type": "boolean",
+                                "example": false
+                              },
+                              "delete_branch_on_merge": {
+                                "description": "Whether to delete head branches when pull requests are merged",
+                                "default": false,
+                                "type": "boolean",
+                                "example": false
+                              },
+                              "allow_merge_commit": {
+                                "description": "Whether to allow merge commits for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "allow_forking": {
+                                "description": "Whether to allow forking this repo",
+                                "type": "boolean"
+                              },
+                              "subscribers_count": {
+                                "type": "integer"
+                              },
+                              "network_count": {
+                                "type": "integer"
+                              },
+                              "open_issues": {
+                                "type": "integer"
+                              },
+                              "watchers": {
+                                "type": "integer"
+                              },
+                              "master_branch": {
+                                "type": "string"
+                              },
+                              "starred_at": {
+                                "type": "string",
+                                "example": "\"2020-07-09T00:17:42Z\""
+                              }
+                            },
+                            "required": [
+                              "archive_url",
+                              "assignees_url",
+                              "blobs_url",
+                              "branches_url",
+                              "collaborators_url",
+                              "comments_url",
+                              "commits_url",
+                              "compare_url",
+                              "contents_url",
+                              "contributors_url",
+                              "deployments_url",
+                              "description",
+                              "downloads_url",
+                              "events_url",
+                              "fork",
+                              "forks_url",
+                              "full_name",
+                              "git_commits_url",
+                              "git_refs_url",
+                              "git_tags_url",
+                              "hooks_url",
+                              "html_url",
+                              "id",
+                              "node_id",
+                              "issue_comment_url",
+                              "issue_events_url",
+                              "issues_url",
+                              "keys_url",
+                              "labels_url",
+                              "languages_url",
+                              "merges_url",
+                              "milestones_url",
+                              "name",
+                              "notifications_url",
+                              "owner",
+                              "private",
+                              "pulls_url",
+                              "releases_url",
+                              "stargazers_url",
+                              "statuses_url",
+                              "subscribers_url",
+                              "subscription_url",
+                              "tags_url",
+                              "teams_url",
+                              "trees_url",
+                              "url",
+                              "clone_url",
+                              "default_branch",
+                              "forks",
+                              "forks_count",
+                              "git_url",
+                              "has_downloads",
+                              "has_issues",
+                              "has_projects",
+                              "has_wiki",
+                              "has_pages",
+                              "homepage",
+                              "language",
+                              "archived",
+                              "disabled",
+                              "mirror_url",
+                              "open_issues",
+                              "open_issues_count",
+                              "license",
+                              "pushed_at",
+                              "size",
+                              "ssh_url",
+                              "stargazers_count",
+                              "svn_url",
+                              "watchers",
+                              "watchers_count",
+                              "created_at",
+                              "updated_at"
+                            ],
+                            "nullable": true
+                          },
+                          "temp_clone_token": {
+                            "type": "string"
+                          },
+                          "delete_branch_on_merge": {
+                            "type": "boolean"
+                          },
+                          "subscribers_count": {
+                            "type": "integer"
+                          },
+                          "network_count": {
+                            "type": "integer"
+                          },
+                          "code_of_conduct": {
+                            "title": "Code Of Conduct",
+                            "description": "Code Of Conduct",
+                            "type": "object",
+                            "properties": {
+                              "key": {
+                                "type": "string",
+                                "example": "contributor_covenant"
+                              },
+                              "name": {
+                                "type": "string",
+                                "example": "Contributor Covenant"
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/codes_of_conduct/contributor_covenant"
+                              },
+                              "body": {
+                                "type": "string",
+                                "example": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.\n\n## Our Standards\n\nExamples of behavior that contributes to creating a positive environment include:\n\n* Using welcoming and inclusive language\n* Being respectful of differing viewpoints and experiences\n* Gracefully accepting constructive criticism\n* Focusing on what is best for the community\n* Showing empathy towards other community members\n\nExamples of unacceptable behavior by participants include:\n\n* The use of sexualized language or imagery and unwelcome sexual attention or advances\n* Trolling, insulting/derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or electronic address, without explicit permission\n* Other conduct which could reasonably be considered inappropriate in a professional setting\n\n## Our Responsibilities\n\nProject maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response\n                  to any instances of unacceptable behavior.\n\nProject maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.\n\n## Scope\n\nThis Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address,\n                  posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [EMAIL]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.\n\nProject maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]\n\n[homepage]: http://contributor-covenant.org\n[version]: http://contributor-covenant.org/version/1/4/\n"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "nullable": true
+                              }
+                            },
+                            "required": [
+                              "url",
+                              "html_url",
+                              "key",
+                              "name"
+                            ]
+                          },
+                          "license": {
+                            "type": "object",
+                            "properties": {
+                              "key": {
+                                "type": "string"
+                              },
+                              "name": {
+                                "type": "string"
+                              },
+                              "spdx_id": {
+                                "type": "string"
+                              },
+                              "url": {
+                                "type": "string"
+                              },
+                              "node_id": {
+                                "type": "string"
+                              }
+                            },
+                            "nullable": true
+                          },
+                          "forks": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "open_issues": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "watchers": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "allow_forking": {
+                            "type": "boolean"
+                          }
+                        },
+                        "required": [
+                          "archive_url",
+                          "assignees_url",
+                          "blobs_url",
+                          "branches_url",
+                          "collaborators_url",
+                          "comments_url",
+                          "commits_url",
+                          "compare_url",
+                          "contents_url",
+                          "contributors_url",
+                          "deployments_url",
+                          "description",
+                          "downloads_url",
+                          "events_url",
+                          "fork",
+                          "forks_url",
+                          "full_name",
+                          "git_commits_url",
+                          "git_refs_url",
+                          "git_tags_url",
+                          "hooks_url",
+                          "html_url",
+                          "id",
+                          "node_id",
+                          "issue_comment_url",
+                          "issue_events_url",
+                          "issues_url",
+                          "keys_url",
+                          "labels_url",
+                          "languages_url",
+                          "merges_url",
+                          "milestones_url",
+                          "name",
+                          "notifications_url",
+                          "owner",
+                          "private",
+                          "pulls_url",
+                          "releases_url",
+                          "stargazers_url",
+                          "statuses_url",
+                          "subscribers_url",
+                          "subscription_url",
+                          "tags_url",
+                          "teams_url",
+                          "trees_url",
+                          "url"
+                        ]
+                      }
+                    },
+                    "required": [
+                      "number",
+                      "created_at",
+                      "url",
+                      "html_url",
+                      "instances_url",
+                      "state",
+                      "dismissed_by",
+                      "dismissed_at",
+                      "dismissed_reason",
+                      "rule",
+                      "tool",
+                      "most_recent_instance",
+                      "repository"
+                    ]
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": [
+                      {
+                        "number": 4,
+                        "created_at": "2020-02-13T12:29:18Z",
+                        "url": "https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/4",
+                        "html_url": "https://github.com/octocat/hello-world/code-scanning/4",
+                        "state": "open",
+                        "dismissed_by": null,
+                        "dismissed_at": null,
+                        "dismissed_reason": null,
+                        "rule": {
+                          "id": "js/zipslip",
+                          "severity": "error",
+                          "tags": [
+                            "security",
+                            "external/cwe/cwe-022"
+                          ],
+                          "description": "Arbitrary file write during zip extraction",
+                          "name": "js/zipslip"
+                        },
+                        "tool": {
+                          "name": "CodeQL",
+                          "guid": null,
+                          "version": "2.4.0"
+                        },
+                        "most_recent_instance": {
+                          "ref": "refs/heads/main",
+                          "analysis_key": ".github/workflows/codeql-analysis.yml:CodeQL-Build",
+                          "environment": "{}",
+                          "state": "open",
+                          "commit_sha": "39406e42cb832f683daa691dd652a8dc36ee8930",
+                          "message": {
+                            "text": "This path depends on a user-provided value."
+                          },
+                          "location": {
+                            "path": "spec-main/api-session-spec.ts",
+                            "start_line": 917,
+                            "end_line": 917,
+                            "start_column": 7,
+                            "end_column": 18
+                          },
+                          "classifications": [
+                            "test"
+                          ]
+                        },
+                        "instances_url": "https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/4/instances",
+                        "repository": {
+                          "id": 1296269,
+                          "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
+                          "name": "Hello-World",
+                          "full_name": "octocat/Hello-World",
+                          "owner": {
+                            "login": "octocat",
+                            "id": 1,
+                            "node_id": "MDQ6VXNlcjE=",
+                            "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                            "gravatar_id": "",
+                            "url": "https://api.github.com/users/octocat",
+                            "html_url": "https://github.com/octocat",
+                            "followers_url": "https://api.github.com/users/octocat/followers",
+                            "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                            "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                            "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                            "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                            "organizations_url": "https://api.github.com/users/octocat/orgs",
+                            "repos_url": "https://api.github.com/users/octocat/repos",
+                            "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                            "received_events_url": "https://api.github.com/users/octocat/received_events",
+                            "type": "User",
+                            "site_admin": false
+                          },
+                          "private": false,
+                          "html_url": "https://github.com/octocat/Hello-World",
+                          "description": "This your first repo!",
+                          "fork": false,
+                          "url": "https://api.github.com/repos/octocat/Hello-World",
+                          "archive_url": "https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}",
+                          "assignees_url": "https://api.github.com/repos/octocat/Hello-World/assignees{/user}",
+                          "blobs_url": "https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}",
+                          "branches_url": "https://api.github.com/repos/octocat/Hello-World/branches{/branch}",
+                          "collaborators_url": "https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}",
+                          "comments_url": "https://api.github.com/repos/octocat/Hello-World/comments{/number}",
+                          "commits_url": "https://api.github.com/repos/octocat/Hello-World/commits{/sha}",
+                          "compare_url": "https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}",
+                          "contents_url": "https://api.github.com/repos/octocat/Hello-World/contents/{+path}",
+                          "contributors_url": "https://api.github.com/repos/octocat/Hello-World/contributors",
+                          "deployments_url": "https://api.github.com/repos/octocat/Hello-World/deployments",
+                          "downloads_url": "https://api.github.com/repos/octocat/Hello-World/downloads",
+                          "events_url": "https://api.github.com/repos/octocat/Hello-World/events",
+                          "forks_url": "https://api.github.com/repos/octocat/Hello-World/forks",
+                          "git_commits_url": "https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}",
+                          "git_refs_url": "https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}",
+                          "git_tags_url": "https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}",
+                          "git_url": "git:github.com/octocat/Hello-World.git",
+                          "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}",
+                          "issue_events_url": "https://api.github.com/repos/octocat/Hello-World/issues/events{/number}",
+                          "issues_url": "https://api.github.com/repos/octocat/Hello-World/issues{/number}",
+                          "keys_url": "https://api.github.com/repos/octocat/Hello-World/keys{/key_id}",
+                          "labels_url": "https://api.github.com/repos/octocat/Hello-World/labels{/name}",
+                          "languages_url": "https://api.github.com/repos/octocat/Hello-World/languages",
+                          "merges_url": "https://api.github.com/repos/octocat/Hello-World/merges",
+                          "milestones_url": "https://api.github.com/repos/octocat/Hello-World/milestones{/number}",
+                          "notifications_url": "https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}",
+                          "pulls_url": "https://api.github.com/repos/octocat/Hello-World/pulls{/number}",
+                          "releases_url": "https://api.github.com/repos/octocat/Hello-World/releases{/id}",
+                          "ssh_url": "git@github.com:octocat/Hello-World.git",
+                          "stargazers_url": "https://api.github.com/repos/octocat/Hello-World/stargazers",
+                          "statuses_url": "https://api.github.com/repos/octocat/Hello-World/statuses/{sha}",
+                          "subscribers_url": "https://api.github.com/repos/octocat/Hello-World/subscribers",
+                          "subscription_url": "https://api.github.com/repos/octocat/Hello-World/subscription",
+                          "tags_url": "https://api.github.com/repos/octocat/Hello-World/tags",
+                          "teams_url": "https://api.github.com/repos/octocat/Hello-World/teams",
+                          "trees_url": "https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}",
+                          "clone_url": "https://github.com/octocat/Hello-World.git",
+                          "mirror_url": "git:git.example.com/octocat/Hello-World",
+                          "hooks_url": "https://api.github.com/repos/octocat/Hello-World/hooks",
+                          "svn_url": "https://svn.github.com/octocat/Hello-World",
+                          "homepage": "https://github.com",
+                          "language": null,
+                          "forks_count": 9,
+                          "stargazers_count": 80,
+                          "watchers_count": 80,
+                          "size": 108,
+                          "default_branch": "master",
+                          "open_issues_count": 0,
+                          "is_template": false,
+                          "topics": [
+                            "octocat",
+                            "atom",
+                            "electron",
+                            "api"
+                          ],
+                          "has_issues": true,
+                          "has_projects": true,
+                          "has_wiki": true,
+                          "has_pages": false,
+                          "has_downloads": true,
+                          "archived": false,
+                          "disabled": false,
+                          "visibility": "public",
+                          "pushed_at": "2011-01-26T19:06:43Z",
+                          "created_at": "2011-01-26T19:01:12Z",
+                          "updated_at": "2011-01-26T19:14:43Z",
+                          "permissions": {
+                            "admin": false,
+                            "push": false,
+                            "pull": true
+                          },
+                          "template_repository": {
+                            "id": 1296269,
+                            "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
+                            "name": "Hello-World-Template",
+                            "full_name": "octocat/Hello-World-Template",
+                            "owner": {
+                              "login": "octocat",
+                              "id": 1,
+                              "node_id": "MDQ6VXNlcjE=",
+                              "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                              "gravatar_id": "",
+                              "url": "https://api.github.com/users/octocat",
+                              "html_url": "https://github.com/octocat",
+                              "followers_url": "https://api.github.com/users/octocat/followers",
+                              "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                              "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                              "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                              "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                              "organizations_url": "https://api.github.com/users/octocat/orgs",
+                              "repos_url": "https://api.github.com/users/octocat/repos",
+                              "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                              "received_events_url": "https://api.github.com/users/octocat/received_events",
+                              "type": "User",
+                              "site_admin": false
+                            },
+                            "private": false,
+                            "html_url": "https://github.com/octocat/Hello-World-Template",
+                            "description": "This your first repo!",
+                            "fork": false,
+                            "url": "https://api.github.com/repos/octocat/Hello-World-Template",
+                            "archive_url": "https://api.github.com/repos/octocat/Hello-World-Template/{archive_format}{/ref}",
+                            "assignees_url": "https://api.github.com/repos/octocat/Hello-World-Template/assignees{/user}",
+                            "blobs_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/blobs{/sha}",
+                            "branches_url": "https://api.github.com/repos/octocat/Hello-World-Template/branches{/branch}",
+                            "collaborators_url": "https://api.github.com/repos/octocat/Hello-World-Template/collaborators{/collaborator}",
+                            "comments_url": "https://api.github.com/repos/octocat/Hello-World-Template/comments{/number}",
+                            "commits_url": "https://api.github.com/repos/octocat/Hello-World-Template/commits{/sha}",
+                            "compare_url": "https://api.github.com/repos/octocat/Hello-World-Template/compare/{base}...{head}",
+                            "contents_url": "https://api.github.com/repos/octocat/Hello-World-Template/contents/{+path}",
+                            "contributors_url": "https://api.github.com/repos/octocat/Hello-World-Template/contributors",
+                            "deployments_url": "https://api.github.com/repos/octocat/Hello-World-Template/deployments",
+                            "downloads_url": "https://api.github.com/repos/octocat/Hello-World-Template/downloads",
+                            "events_url": "https://api.github.com/repos/octocat/Hello-World-Template/events",
+                            "forks_url": "https://api.github.com/repos/octocat/Hello-World-Template/forks",
+                            "git_commits_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/commits{/sha}",
+                            "git_refs_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/refs{/sha}",
+                            "git_tags_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/tags{/sha}",
+                            "git_url": "git:github.com/octocat/Hello-World-Template.git",
+                            "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues/comments{/number}",
+                            "issue_events_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues/events{/number}",
+                            "issues_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues{/number}",
+                            "keys_url": "https://api.github.com/repos/octocat/Hello-World-Template/keys{/key_id}",
+                            "labels_url": "https://api.github.com/repos/octocat/Hello-World-Template/labels{/name}",
+                            "languages_url": "https://api.github.com/repos/octocat/Hello-World-Template/languages",
+                            "merges_url": "https://api.github.com/repos/octocat/Hello-World-Template/merges",
+                            "milestones_url": "https://api.github.com/repos/octocat/Hello-World-Template/milestones{/number}",
+                            "notifications_url": "https://api.github.com/repos/octocat/Hello-World-Template/notifications{?since,all,participating}",
+                            "pulls_url": "https://api.github.com/repos/octocat/Hello-World-Template/pulls{/number}",
+                            "releases_url": "https://api.github.com/repos/octocat/Hello-World-Template/releases{/id}",
+                            "ssh_url": "git@github.com:octocat/Hello-World-Template.git",
+                            "stargazers_url": "https://api.github.com/repos/octocat/Hello-World-Template/stargazers",
+                            "statuses_url": "https://api.github.com/repos/octocat/Hello-World-Template/statuses/{sha}",
+                            "subscribers_url": "https://api.github.com/repos/octocat/Hello-World-Template/subscribers",
+                            "subscription_url": "https://api.github.com/repos/octocat/Hello-World-Template/subscription",
+                            "tags_url": "https://api.github.com/repos/octocat/Hello-World-Template/tags",
+                            "teams_url": "https://api.github.com/repos/octocat/Hello-World-Template/teams",
+                            "trees_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/trees{/sha}",
+                            "clone_url": "https://github.com/octocat/Hello-World-Template.git",
+                            "mirror_url": "git:git.example.com/octocat/Hello-World-Template",
+                            "hooks_url": "https://api.github.com/repos/octocat/Hello-World-Template/hooks",
+                            "svn_url": "https://svn.github.com/octocat/Hello-World-Template",
+                            "homepage": "https://github.com",
+                            "language": null,
+                            "forks": 9,
+                            "forks_count": 9,
+                            "stargazers_count": 80,
+                            "watchers_count": 80,
+                            "watchers": 80,
+                            "size": 108,
+                            "default_branch": "master",
+                            "open_issues": 0,
+                            "open_issues_count": 0,
+                            "is_template": true,
+                            "license": {
+                              "key": "mit",
+                              "name": "MIT License",
+                              "url": "https://api.github.com/licenses/mit",
+                              "spdx_id": "MIT",
+                              "node_id": "MDc6TGljZW5zZW1pdA==",
+                              "html_url": "https://api.github.com/licenses/mit"
+                            },
+                            "topics": [
+                              "octocat",
+                              "atom",
+                              "electron",
+                              "api"
+                            ],
+                            "has_issues": true,
+                            "has_projects": true,
+                            "has_wiki": true,
+                            "has_pages": false,
+                            "has_downloads": true,
+                            "archived": false,
+                            "disabled": false,
+                            "visibility": "public",
+                            "pushed_at": "2011-01-26T19:06:43Z",
+                            "created_at": "2011-01-26T19:01:12Z",
+                            "updated_at": "2011-01-26T19:14:43Z",
+                            "permissions": {
+                              "admin": false,
+                              "push": false,
+                              "pull": true
+                            },
+                            "allow_rebase_merge": true,
+                            "temp_clone_token": "ABTLWHOULUVAXGTRYU7OC2876QJ2O",
+                            "allow_squash_merge": true,
+                            "allow_auto_merge": false,
+                            "delete_branch_on_merge": true,
+                            "allow_merge_commit": true,
+                            "subscribers_count": 42,
+                            "network_count": 0
+                          }
+                        }
+                      },
+                      {
+                        "number": 3,
+                        "created_at": "2020-02-13T12:29:18Z",
+                        "url": "https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/3",
+                        "html_url": "https://github.com/octocat/hello-world/code-scanning/3",
+                        "state": "dismissed",
+                        "dismissed_by": {
+                          "login": "octocat",
+                          "id": 1,
+                          "node_id": "MDQ6VXNlcjE=",
+                          "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                          "gravatar_id": "",
+                          "url": "https://api.github.com/users/octocat",
+                          "html_url": "https://github.com/octocat",
+                          "followers_url": "https://api.github.com/users/octocat/followers",
+                          "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                          "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                          "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                          "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                          "organizations_url": "https://api.github.com/users/octocat/orgs",
+                          "repos_url": "https://api.github.com/users/octocat/repos",
+                          "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                          "received_events_url": "https://api.github.com/users/octocat/received_events",
+                          "type": "User",
+                          "site_admin": false
+                        },
+                        "dismissed_at": "2020-02-14T12:29:18Z",
+                        "dismissed_reason": "false positive",
+                        "rule": {
+                          "id": "js/zipslip",
+                          "severity": "error",
+                          "tags": [
+                            "security",
+                            "external/cwe/cwe-022"
+                          ],
+                          "description": "Arbitrary file write during zip extraction",
+                          "name": "js/zipslip"
+                        },
+                        "tool": {
+                          "name": "CodeQL",
+                          "guid": null,
+                          "version": "2.4.0"
+                        },
+                        "most_recent_instance": {
+                          "ref": "refs/heads/main",
+                          "analysis_key": ".github/workflows/codeql-analysis.yml:CodeQL-Build",
+                          "environment": "{}",
+                          "state": "open",
+                          "commit_sha": "39406e42cb832f683daa691dd652a8dc36ee8930",
+                          "message": {
+                            "text": "This path depends on a user-provided value."
+                          },
+                          "location": {
+                            "path": "lib/ab12-gen.js",
+                            "start_line": 917,
+                            "end_line": 917,
+                            "start_column": 7,
+                            "end_column": 18
+                          },
+                          "classifications": [
+
+                          ]
+                        },
+                        "instances_url": "https://api.github.com/repos/octocat/hello-world/code-scanning/alerts/3/instances",
+                        "repository": {
+                          "id": 1296269,
+                          "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
+                          "name": "Hello-World",
+                          "full_name": "octocat/Hello-World",
+                          "owner": {
+                            "login": "octocat",
+                            "id": 1,
+                            "node_id": "MDQ6VXNlcjE=",
+                            "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                            "gravatar_id": "",
+                            "url": "https://api.github.com/users/octocat",
+                            "html_url": "https://github.com/octocat",
+                            "followers_url": "https://api.github.com/users/octocat/followers",
+                            "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                            "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                            "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                            "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                            "organizations_url": "https://api.github.com/users/octocat/orgs",
+                            "repos_url": "https://api.github.com/users/octocat/repos",
+                            "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                            "received_events_url": "https://api.github.com/users/octocat/received_events",
+                            "type": "User",
+                            "site_admin": false
+                          },
+                          "private": false,
+                          "html_url": "https://github.com/octocat/Hello-World",
+                          "description": "This your first repo!",
+                          "fork": false,
+                          "url": "https://api.github.com/repos/octocat/Hello-World",
+                          "archive_url": "https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}",
+                          "assignees_url": "https://api.github.com/repos/octocat/Hello-World/assignees{/user}",
+                          "blobs_url": "https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}",
+                          "branches_url": "https://api.github.com/repos/octocat/Hello-World/branches{/branch}",
+                          "collaborators_url": "https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}",
+                          "comments_url": "https://api.github.com/repos/octocat/Hello-World/comments{/number}",
+                          "commits_url": "https://api.github.com/repos/octocat/Hello-World/commits{/sha}",
+                          "compare_url": "https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}",
+                          "contents_url": "https://api.github.com/repos/octocat/Hello-World/contents/{+path}",
+                          "contributors_url": "https://api.github.com/repos/octocat/Hello-World/contributors",
+                          "deployments_url": "https://api.github.com/repos/octocat/Hello-World/deployments",
+                          "downloads_url": "https://api.github.com/repos/octocat/Hello-World/downloads",
+                          "events_url": "https://api.github.com/repos/octocat/Hello-World/events",
+                          "forks_url": "https://api.github.com/repos/octocat/Hello-World/forks",
+                          "git_commits_url": "https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}",
+                          "git_refs_url": "https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}",
+                          "git_tags_url": "https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}",
+                          "git_url": "git:github.com/octocat/Hello-World.git",
+                          "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}",
+                          "issue_events_url": "https://api.github.com/repos/octocat/Hello-World/issues/events{/number}",
+                          "issues_url": "https://api.github.com/repos/octocat/Hello-World/issues{/number}",
+                          "keys_url": "https://api.github.com/repos/octocat/Hello-World/keys{/key_id}",
+                          "labels_url": "https://api.github.com/repos/octocat/Hello-World/labels{/name}",
+                          "languages_url": "https://api.github.com/repos/octocat/Hello-World/languages",
+                          "merges_url": "https://api.github.com/repos/octocat/Hello-World/merges",
+                          "milestones_url": "https://api.github.com/repos/octocat/Hello-World/milestones{/number}",
+                          "notifications_url": "https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}",
+                          "pulls_url": "https://api.github.com/repos/octocat/Hello-World/pulls{/number}",
+                          "releases_url": "https://api.github.com/repos/octocat/Hello-World/releases{/id}",
+                          "ssh_url": "git@github.com:octocat/Hello-World.git",
+                          "stargazers_url": "https://api.github.com/repos/octocat/Hello-World/stargazers",
+                          "statuses_url": "https://api.github.com/repos/octocat/Hello-World/statuses/{sha}",
+                          "subscribers_url": "https://api.github.com/repos/octocat/Hello-World/subscribers",
+                          "subscription_url": "https://api.github.com/repos/octocat/Hello-World/subscription",
+                          "tags_url": "https://api.github.com/repos/octocat/Hello-World/tags",
+                          "teams_url": "https://api.github.com/repos/octocat/Hello-World/teams",
+                          "trees_url": "https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}",
+                          "clone_url": "https://github.com/octocat/Hello-World.git",
+                          "mirror_url": "git:git.example.com/octocat/Hello-World",
+                          "hooks_url": "https://api.github.com/repos/octocat/Hello-World/hooks",
+                          "svn_url": "https://svn.github.com/octocat/Hello-World",
+                          "homepage": "https://github.com",
+                          "language": null,
+                          "forks_count": 9,
+                          "stargazers_count": 80,
+                          "watchers_count": 80,
+                          "size": 108,
+                          "default_branch": "master",
+                          "open_issues_count": 0,
+                          "is_template": false,
+                          "topics": [
+                            "octocat",
+                            "atom",
+                            "electron",
+                            "api"
+                          ],
+                          "has_issues": true,
+                          "has_projects": true,
+                          "has_wiki": true,
+                          "has_pages": false,
+                          "has_downloads": true,
+                          "archived": false,
+                          "disabled": false,
+                          "visibility": "public",
+                          "pushed_at": "2011-01-26T19:06:43Z",
+                          "created_at": "2011-01-26T19:01:12Z",
+                          "updated_at": "2011-01-26T19:14:43Z",
+                          "permissions": {
+                            "admin": false,
+                            "push": false,
+                            "pull": true
+                          },
+                          "template_repository": {
+                            "id": 1296269,
+                            "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
+                            "name": "Hello-World-Template",
+                            "full_name": "octocat/Hello-World-Template",
+                            "owner": {
+                              "login": "octocat",
+                              "id": 1,
+                              "node_id": "MDQ6VXNlcjE=",
+                              "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                              "gravatar_id": "",
+                              "url": "https://api.github.com/users/octocat",
+                              "html_url": "https://github.com/octocat",
+                              "followers_url": "https://api.github.com/users/octocat/followers",
+                              "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                              "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                              "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                              "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                              "organizations_url": "https://api.github.com/users/octocat/orgs",
+                              "repos_url": "https://api.github.com/users/octocat/repos",
+                              "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                              "received_events_url": "https://api.github.com/users/octocat/received_events",
+                              "type": "User",
+                              "site_admin": false
+                            },
+                            "private": false,
+                            "html_url": "https://github.com/octocat/Hello-World-Template",
+                            "description": "This your first repo!",
+                            "fork": false,
+                            "url": "https://api.github.com/repos/octocat/Hello-World-Template",
+                            "archive_url": "https://api.github.com/repos/octocat/Hello-World-Template/{archive_format}{/ref}",
+                            "assignees_url": "https://api.github.com/repos/octocat/Hello-World-Template/assignees{/user}",
+                            "blobs_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/blobs{/sha}",
+                            "branches_url": "https://api.github.com/repos/octocat/Hello-World-Template/branches{/branch}",
+                            "collaborators_url": "https://api.github.com/repos/octocat/Hello-World-Template/collaborators{/collaborator}",
+                            "comments_url": "https://api.github.com/repos/octocat/Hello-World-Template/comments{/number}",
+                            "commits_url": "https://api.github.com/repos/octocat/Hello-World-Template/commits{/sha}",
+                            "compare_url": "https://api.github.com/repos/octocat/Hello-World-Template/compare/{base}...{head}",
+                            "contents_url": "https://api.github.com/repos/octocat/Hello-World-Template/contents/{+path}",
+                            "contributors_url": "https://api.github.com/repos/octocat/Hello-World-Template/contributors",
+                            "deployments_url": "https://api.github.com/repos/octocat/Hello-World-Template/deployments",
+                            "downloads_url": "https://api.github.com/repos/octocat/Hello-World-Template/downloads",
+                            "events_url": "https://api.github.com/repos/octocat/Hello-World-Template/events",
+                            "forks_url": "https://api.github.com/repos/octocat/Hello-World-Template/forks",
+                            "git_commits_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/commits{/sha}",
+                            "git_refs_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/refs{/sha}",
+                            "git_tags_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/tags{/sha}",
+                            "git_url": "git:github.com/octocat/Hello-World-Template.git",
+                            "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues/comments{/number}",
+                            "issue_events_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues/events{/number}",
+                            "issues_url": "https://api.github.com/repos/octocat/Hello-World-Template/issues{/number}",
+                            "keys_url": "https://api.github.com/repos/octocat/Hello-World-Template/keys{/key_id}",
+                            "labels_url": "https://api.github.com/repos/octocat/Hello-World-Template/labels{/name}",
+                            "languages_url": "https://api.github.com/repos/octocat/Hello-World-Template/languages",
+                            "merges_url": "https://api.github.com/repos/octocat/Hello-World-Template/merges",
+                            "milestones_url": "https://api.github.com/repos/octocat/Hello-World-Template/milestones{/number}",
+                            "notifications_url": "https://api.github.com/repos/octocat/Hello-World-Template/notifications{?since,all,participating}",
+                            "pulls_url": "https://api.github.com/repos/octocat/Hello-World-Template/pulls{/number}",
+                            "releases_url": "https://api.github.com/repos/octocat/Hello-World-Template/releases{/id}",
+                            "ssh_url": "git@github.com:octocat/Hello-World-Template.git",
+                            "stargazers_url": "https://api.github.com/repos/octocat/Hello-World-Template/stargazers",
+                            "statuses_url": "https://api.github.com/repos/octocat/Hello-World-Template/statuses/{sha}",
+                            "subscribers_url": "https://api.github.com/repos/octocat/Hello-World-Template/subscribers",
+                            "subscription_url": "https://api.github.com/repos/octocat/Hello-World-Template/subscription",
+                            "tags_url": "https://api.github.com/repos/octocat/Hello-World-Template/tags",
+                            "teams_url": "https://api.github.com/repos/octocat/Hello-World-Template/teams",
+                            "trees_url": "https://api.github.com/repos/octocat/Hello-World-Template/git/trees{/sha}",
+                            "clone_url": "https://github.com/octocat/Hello-World-Template.git",
+                            "mirror_url": "git:git.example.com/octocat/Hello-World-Template",
+                            "hooks_url": "https://api.github.com/repos/octocat/Hello-World-Template/hooks",
+                            "svn_url": "https://svn.github.com/octocat/Hello-World-Template",
+                            "homepage": "https://github.com",
+                            "language": null,
+                            "forks": 9,
+                            "forks_count": 9,
+                            "stargazers_count": 80,
+                            "watchers_count": 80,
+                            "watchers": 80,
+                            "size": 108,
+                            "default_branch": "master",
+                            "open_issues": 0,
+                            "open_issues_count": 0,
+                            "is_template": true,
+                            "license": {
+                              "key": "mit",
+                              "name": "MIT License",
+                              "url": "https://api.github.com/licenses/mit",
+                              "spdx_id": "MIT",
+                              "node_id": "MDc6TGljZW5zZW1pdA==",
+                              "html_url": "https://api.github.com/licenses/mit"
+                            },
+                            "topics": [
+                              "octocat",
+                              "atom",
+                              "electron",
+                              "api"
+                            ],
+                            "has_issues": true,
+                            "has_projects": true,
+                            "has_wiki": true,
+                            "has_pages": false,
+                            "has_downloads": true,
+                            "archived": false,
+                            "disabled": false,
+                            "visibility": "public",
+                            "pushed_at": "2011-01-26T19:06:43Z",
+                            "created_at": "2011-01-26T19:01:12Z",
+                            "updated_at": "2011-01-26T19:14:43Z",
+                            "permissions": {
+                              "admin": false,
+                              "push": false,
+                              "pull": true
+                            },
+                            "allow_rebase_merge": true,
+                            "temp_clone_token": "ABTLWHOULUVAXGTRYU7OC2876QJ2O",
+                            "allow_squash_merge": true,
+                            "allow_auto_merge": false,
+                            "delete_branch_on_merge": true,
+                            "allow_merge_commit": true,
+                            "subscribers_count": 42,
+                            "network_count": 0
+                          }
+                        }
+                      }
+                    ]
+                  }
+                }
+              }
+            },
+            "headers": {
+              "Link": {
+                "example": "<https://api.github.com/resource?page=2>; rel=\"next\", <https://api.github.com/resource?page=5>; rel=\"last\"",
+                "schema": {
+                  "type": "string"
+                }
+              }
+            }
+          },
+          "403": {
+            "description": "Response if GitHub Advanced Security is not enabled for this repository",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "Basic Error",
+                  "description": "Basic Error",
+                  "type": "object",
+                  "properties": {
+                    "message": {
+                      "type": "string"
+                    },
+                    "documentation_url": {
+                      "type": "string"
+                    },
+                    "url": {
+                      "type": "string"
+                    },
+                    "status": {
+                      "type": "string"
+                    }
+                  }
+                }
+              }
+            }
+          },
+          "404": {
+            "description": "Resource not found",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "Basic Error",
+                  "description": "Basic Error",
+                  "type": "object",
+                  "properties": {
+                    "message": {
+                      "type": "string"
+                    },
+                    "documentation_url": {
+                      "type": "string"
+                    },
+                    "url": {
+                      "type": "string"
+                    },
+                    "status": {
+                      "type": "string"
+                    }
+                  }
+                }
+              }
+            }
+          },
+          "503": {
+            "description": "Service unavailable",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "object",
+                  "properties": {
+                    "code": {
+                      "type": "string"
+                    },
+                    "message": {
+                      "type": "string"
+                    },
+                    "documentation_url": {
+                      "type": "string"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "code-scanning",
+          "subcategory": null
+        }
+      }
+    },
     "/orgs/{org}/credential-authorizations": {
       "get": {
         "summary": "List SAML SSO authorizations for an organization",
@@ -103552,11 +106360,10 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
@@ -103572,7 +106379,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -137300,6 +140107,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -153360,6 +156168,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -287969,7 +290778,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -288270,7 +291079,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/rest/static/dereferenced/ghes-3.0.deref.json b/lib/rest/static/dereferenced/ghes-3.0.deref.json
index 9e2b77f173..233d9bd41e 100644
--- a/lib/rest/static/dereferenced/ghes-3.0.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json
@@ -82014,17 +82014,20 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
                   "parent_team_id": {
                     "type": "integer",
                     "description": "The ID of a team to set as the parent team."
+                  },
+                  "ldap_dn": {
+                    "type": "string",
+                    "description": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.0/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.0/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\""
                   }
                 },
                 "required": [
@@ -82034,7 +82037,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -114471,6 +114474,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -124261,6 +124265,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.0/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -239968,7 +239973,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -240269,7 +240274,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.0/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json
index 53cd68be61..d462630812 100644
--- a/lib/rest/static/dereferenced/ghes-3.1.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json
@@ -82039,17 +82039,20 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
                   "parent_team_id": {
                     "type": "integer",
                     "description": "The ID of a team to set as the parent team."
+                  },
+                  "ldap_dn": {
+                    "type": "string",
+                    "description": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.1/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\""
                   }
                 },
                 "required": [
@@ -82059,7 +82062,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -114496,6 +114499,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -124286,6 +124290,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.1/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -242667,7 +242672,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -242968,7 +242973,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.1/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json
index fd41735784..36586c388d 100644
--- a/lib/rest/static/dereferenced/ghes-3.2.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json
@@ -83994,17 +83994,20 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
                   "parent_team_id": {
                     "type": "integer",
                     "description": "The ID of a team to set as the parent team."
+                  },
+                  "ldap_dn": {
+                    "type": "string",
+                    "description": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.2/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\""
                   }
                 },
                 "required": [
@@ -84014,7 +84017,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -116675,6 +116678,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -127889,6 +127893,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.2/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -249402,7 +249407,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -249703,7 +249708,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.2/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json
index e5029cd0db..0ac4c551aa 100644
--- a/lib/rest/static/dereferenced/ghes-3.3.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json
@@ -87063,17 +87063,20 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
                   "parent_team_id": {
                     "type": "integer",
                     "description": "The ID of a team to set as the parent team."
+                  },
+                  "ldap_dn": {
+                    "type": "string",
+                    "description": "The [distinguished name](https://www.ldap.com/ldap-dns-and-rdns) (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the \"[Update LDAP mapping for a team](https://docs.github.com/enterprise-server@3.3/rest/reference/enterprise-admin#update-ldap-mapping-for-a-team)\" endpoint to change the LDAP DN. For more information, see \"[Using LDAP](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap#enabling-ldap-sync).\""
                   }
                 },
                 "required": [
@@ -87083,7 +87086,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -119060,6 +119063,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -127394,4357 +127398,6 @@
         }
       }
     },
-    "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}": {
-      "get": {
-        "summary": "Get a workflow run attempt",
-        "description": "Gets a specific workflow run attempt. Anyone with read access to the repository\ncan use this endpoint. If the repository is private you must use an access token\nwith the `repo` scope. GitHub Apps must have the `actions:read` permission to\nuse this endpoint.",
-        "tags": [
-          "actions"
-        ],
-        "operationId": "actions/get-workflow-run-attempt",
-        "externalDocs": {
-          "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/actions#get-a-workflow-run-attempt"
-        },
-        "parameters": [
-          {
-            "name": "owner",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "repo",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "run_id",
-            "description": "The id of the workflow run.",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          },
-          {
-            "name": "attempt_number",
-            "description": "The attempt number of the workflow run.",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          },
-          {
-            "name": "exclude_pull_requests",
-            "description": "If `true` pull requests are omitted from the response (empty array).",
-            "in": "query",
-            "required": false,
-            "schema": {
-              "type": "boolean",
-              "default": false
-            }
-          }
-        ],
-        "responses": {
-          "200": {
-            "description": "Response",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Workflow Run",
-                  "description": "An invocation of a workflow",
-                  "type": "object",
-                  "properties": {
-                    "id": {
-                      "type": "integer",
-                      "description": "The ID of the workflow run.",
-                      "example": 5
-                    },
-                    "name": {
-                      "type": "string",
-                      "description": "The name of the workflow run.",
-                      "nullable": true,
-                      "example": "Build"
-                    },
-                    "node_id": {
-                      "type": "string",
-                      "example": "MDEwOkNoZWNrU3VpdGU1"
-                    },
-                    "check_suite_id": {
-                      "type": "integer",
-                      "description": "The ID of the associated check suite.",
-                      "example": 42
-                    },
-                    "check_suite_node_id": {
-                      "type": "string",
-                      "description": "The node ID of the associated check suite.",
-                      "example": "MDEwOkNoZWNrU3VpdGU0Mg=="
-                    },
-                    "head_branch": {
-                      "type": "string",
-                      "nullable": true,
-                      "example": "master"
-                    },
-                    "head_sha": {
-                      "description": "The SHA of the head commit that points to the version of the worflow being run.",
-                      "example": "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d",
-                      "type": "string"
-                    },
-                    "run_number": {
-                      "type": "integer",
-                      "description": "The auto incrementing run number for the workflow run.",
-                      "example": 106
-                    },
-                    "run_attempt": {
-                      "type": "integer",
-                      "description": "Attempt number of the run, 1 for first attempt and higher if the workflow was re-run.",
-                      "example": 1
-                    },
-                    "event": {
-                      "type": "string",
-                      "example": "push"
-                    },
-                    "status": {
-                      "type": "string",
-                      "nullable": true,
-                      "example": "completed"
-                    },
-                    "conclusion": {
-                      "type": "string",
-                      "nullable": true,
-                      "example": "neutral"
-                    },
-                    "workflow_id": {
-                      "type": "integer",
-                      "description": "The ID of the parent workflow.",
-                      "example": 5
-                    },
-                    "url": {
-                      "type": "string",
-                      "description": "The URL to the workflow run.",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5"
-                    },
-                    "html_url": {
-                      "type": "string",
-                      "example": "https://github.com/github/hello-world/suites/4"
-                    },
-                    "pull_requests": {
-                      "type": "array",
-                      "nullable": true,
-                      "items": {
-                        "title": "Pull Request Minimal",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "type": "integer"
-                          },
-                          "number": {
-                            "type": "integer"
-                          },
-                          "url": {
-                            "type": "string"
-                          },
-                          "head": {
-                            "type": "object",
-                            "properties": {
-                              "ref": {
-                                "type": "string"
-                              },
-                              "sha": {
-                                "type": "string"
-                              },
-                              "repo": {
-                                "type": "object",
-                                "properties": {
-                                  "id": {
-                                    "type": "integer"
-                                  },
-                                  "url": {
-                                    "type": "string"
-                                  },
-                                  "name": {
-                                    "type": "string"
-                                  }
-                                },
-                                "required": [
-                                  "id",
-                                  "url",
-                                  "name"
-                                ]
-                              }
-                            },
-                            "required": [
-                              "ref",
-                              "sha",
-                              "repo"
-                            ]
-                          },
-                          "base": {
-                            "type": "object",
-                            "properties": {
-                              "ref": {
-                                "type": "string"
-                              },
-                              "sha": {
-                                "type": "string"
-                              },
-                              "repo": {
-                                "type": "object",
-                                "properties": {
-                                  "id": {
-                                    "type": "integer"
-                                  },
-                                  "url": {
-                                    "type": "string"
-                                  },
-                                  "name": {
-                                    "type": "string"
-                                  }
-                                },
-                                "required": [
-                                  "id",
-                                  "url",
-                                  "name"
-                                ]
-                              }
-                            },
-                            "required": [
-                              "ref",
-                              "sha",
-                              "repo"
-                            ]
-                          }
-                        },
-                        "required": [
-                          "id",
-                          "number",
-                          "url",
-                          "head",
-                          "base"
-                        ]
-                      }
-                    },
-                    "created_at": {
-                      "type": "string",
-                      "format": "date-time"
-                    },
-                    "updated_at": {
-                      "type": "string",
-                      "format": "date-time"
-                    },
-                    "run_started_at": {
-                      "type": "string",
-                      "format": "date-time",
-                      "description": "The start time of the latest run. Resets on re-run."
-                    },
-                    "jobs_url": {
-                      "description": "The URL to the jobs for the workflow run.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/jobs"
-                    },
-                    "logs_url": {
-                      "description": "The URL to download the logs for the workflow run.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/logs"
-                    },
-                    "check_suite_url": {
-                      "description": "The URL to the associated check suite.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/check-suites/12"
-                    },
-                    "artifacts_url": {
-                      "description": "The URL to the artifacts for the workflow run.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun/artifacts"
-                    },
-                    "cancel_url": {
-                      "description": "The URL to cancel the workflow run.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/cancel"
-                    },
-                    "rerun_url": {
-                      "description": "The URL to rerun the workflow run.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun"
-                    },
-                    "previous_attempt_url": {
-                      "nullable": true,
-                      "description": "The URL to the previous attempted run of this workflow, if one exists.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3"
-                    },
-                    "workflow_url": {
-                      "description": "The URL to the workflow.",
-                      "type": "string",
-                      "example": "https://api.github.com/repos/github/hello-world/actions/workflows/main.yaml"
-                    },
-                    "head_commit": {
-                      "title": "Simple Commit",
-                      "description": "Simple Commit",
-                      "type": "object",
-                      "properties": {
-                        "id": {
-                          "type": "string"
-                        },
-                        "tree_id": {
-                          "type": "string"
-                        },
-                        "message": {
-                          "type": "string"
-                        },
-                        "timestamp": {
-                          "type": "string",
-                          "format": "date-time"
-                        },
-                        "author": {
-                          "type": "object",
-                          "properties": {
-                            "name": {
-                              "type": "string"
-                            },
-                            "email": {
-                              "type": "string"
-                            }
-                          },
-                          "required": [
-                            "name",
-                            "email"
-                          ],
-                          "nullable": true
-                        },
-                        "committer": {
-                          "type": "object",
-                          "properties": {
-                            "name": {
-                              "type": "string"
-                            },
-                            "email": {
-                              "type": "string"
-                            }
-                          },
-                          "required": [
-                            "name",
-                            "email"
-                          ],
-                          "nullable": true
-                        }
-                      },
-                      "required": [
-                        "id",
-                        "tree_id",
-                        "message",
-                        "timestamp",
-                        "author",
-                        "committer"
-                      ],
-                      "nullable": true
-                    },
-                    "repository": {
-                      "title": "Minimal Repository",
-                      "description": "Minimal Repository",
-                      "type": "object",
-                      "properties": {
-                        "id": {
-                          "type": "integer",
-                          "example": 1296269
-                        },
-                        "node_id": {
-                          "type": "string",
-                          "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
-                        },
-                        "name": {
-                          "type": "string",
-                          "example": "Hello-World"
-                        },
-                        "full_name": {
-                          "type": "string",
-                          "example": "octocat/Hello-World"
-                        },
-                        "owner": {
-                          "title": "Simple User",
-                          "description": "Simple User",
-                          "type": "object",
-                          "properties": {
-                            "name": {
-                              "nullable": true,
-                              "type": "string"
-                            },
-                            "email": {
-                              "nullable": true,
-                              "type": "string"
-                            },
-                            "login": {
-                              "type": "string",
-                              "example": "octocat"
-                            },
-                            "id": {
-                              "type": "integer",
-                              "example": 1
-                            },
-                            "node_id": {
-                              "type": "string",
-                              "example": "MDQ6VXNlcjE="
-                            },
-                            "avatar_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/images/error/octocat_happy.gif"
-                            },
-                            "gravatar_id": {
-                              "type": "string",
-                              "example": "41d064eb2195891e12d0413f63227ea7",
-                              "nullable": true
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/octocat"
-                            },
-                            "followers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/followers"
-                            },
-                            "following_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/following{/other_user}"
-                            },
-                            "gists_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                            },
-                            "starred_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                            },
-                            "subscriptions_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/subscriptions"
-                            },
-                            "organizations_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/orgs"
-                            },
-                            "repos_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/repos"
-                            },
-                            "events_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/events{/privacy}"
-                            },
-                            "received_events_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/received_events"
-                            },
-                            "type": {
-                              "type": "string",
-                              "example": "User"
-                            },
-                            "site_admin": {
-                              "type": "boolean"
-                            },
-                            "starred_at": {
-                              "type": "string",
-                              "example": "\"2020-07-09T00:17:55Z\""
-                            }
-                          },
-                          "required": [
-                            "avatar_url",
-                            "events_url",
-                            "followers_url",
-                            "following_url",
-                            "gists_url",
-                            "gravatar_id",
-                            "html_url",
-                            "id",
-                            "node_id",
-                            "login",
-                            "organizations_url",
-                            "received_events_url",
-                            "repos_url",
-                            "site_admin",
-                            "starred_url",
-                            "subscriptions_url",
-                            "type",
-                            "url"
-                          ]
-                        },
-                        "private": {
-                          "type": "boolean"
-                        },
-                        "html_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "https://github.com/octocat/Hello-World"
-                        },
-                        "description": {
-                          "type": "string",
-                          "example": "This your first repo!",
-                          "nullable": true
-                        },
-                        "fork": {
-                          "type": "boolean"
-                        },
-                        "url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "https://api.github.com/repos/octocat/Hello-World"
-                        },
-                        "archive_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
-                        },
-                        "assignees_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
-                        },
-                        "blobs_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
-                        },
-                        "branches_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
-                        },
-                        "collaborators_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
-                        },
-                        "comments_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
-                        },
-                        "commits_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
-                        },
-                        "compare_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
-                        },
-                        "contents_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
-                        },
-                        "contributors_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
-                        },
-                        "deployments_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
-                        },
-                        "downloads_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
-                        },
-                        "events_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/events"
-                        },
-                        "forks_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/forks"
-                        },
-                        "git_commits_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
-                        },
-                        "git_refs_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
-                        },
-                        "git_tags_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
-                        },
-                        "git_url": {
-                          "type": "string"
-                        },
-                        "issue_comment_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
-                        },
-                        "issue_events_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
-                        },
-                        "issues_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
-                        },
-                        "keys_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
-                        },
-                        "labels_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
-                        },
-                        "languages_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/languages"
-                        },
-                        "merges_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/merges"
-                        },
-                        "milestones_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
-                        },
-                        "notifications_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
-                        },
-                        "pulls_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
-                        },
-                        "releases_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
-                        },
-                        "ssh_url": {
-                          "type": "string"
-                        },
-                        "stargazers_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
-                        },
-                        "statuses_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
-                        },
-                        "subscribers_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
-                        },
-                        "subscription_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
-                        },
-                        "tags_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/tags"
-                        },
-                        "teams_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/teams"
-                        },
-                        "trees_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
-                        },
-                        "clone_url": {
-                          "type": "string"
-                        },
-                        "mirror_url": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "hooks_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
-                        },
-                        "svn_url": {
-                          "type": "string"
-                        },
-                        "homepage": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "language": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "forks_count": {
-                          "type": "integer"
-                        },
-                        "stargazers_count": {
-                          "type": "integer"
-                        },
-                        "watchers_count": {
-                          "type": "integer"
-                        },
-                        "size": {
-                          "type": "integer"
-                        },
-                        "default_branch": {
-                          "type": "string"
-                        },
-                        "open_issues_count": {
-                          "type": "integer"
-                        },
-                        "is_template": {
-                          "type": "boolean"
-                        },
-                        "topics": {
-                          "type": "array",
-                          "items": {
-                            "type": "string"
-                          }
-                        },
-                        "has_issues": {
-                          "type": "boolean"
-                        },
-                        "has_projects": {
-                          "type": "boolean"
-                        },
-                        "has_wiki": {
-                          "type": "boolean"
-                        },
-                        "has_pages": {
-                          "type": "boolean"
-                        },
-                        "has_downloads": {
-                          "type": "boolean"
-                        },
-                        "archived": {
-                          "type": "boolean"
-                        },
-                        "disabled": {
-                          "type": "boolean"
-                        },
-                        "visibility": {
-                          "type": "string"
-                        },
-                        "pushed_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:06:43Z",
-                          "nullable": true
-                        },
-                        "created_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:01:12Z",
-                          "nullable": true
-                        },
-                        "updated_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:14:43Z",
-                          "nullable": true
-                        },
-                        "permissions": {
-                          "type": "object",
-                          "properties": {
-                            "admin": {
-                              "type": "boolean"
-                            },
-                            "maintain": {
-                              "type": "boolean"
-                            },
-                            "push": {
-                              "type": "boolean"
-                            },
-                            "triage": {
-                              "type": "boolean"
-                            },
-                            "pull": {
-                              "type": "boolean"
-                            }
-                          }
-                        },
-                        "template_repository": {
-                          "title": "Repository",
-                          "description": "A git repository",
-                          "type": "object",
-                          "properties": {
-                            "id": {
-                              "description": "Unique identifier of the repository",
-                              "example": 42,
-                              "type": "integer"
-                            },
-                            "node_id": {
-                              "type": "string",
-                              "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
-                            },
-                            "name": {
-                              "description": "The name of the repository.",
-                              "type": "string",
-                              "example": "Team Environment"
-                            },
-                            "full_name": {
-                              "type": "string",
-                              "example": "octocat/Hello-World"
-                            },
-                            "license": {
-                              "title": "License Simple",
-                              "description": "License Simple",
-                              "type": "object",
-                              "properties": {
-                                "key": {
-                                  "type": "string",
-                                  "example": "mit"
-                                },
-                                "name": {
-                                  "type": "string",
-                                  "example": "MIT License"
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "nullable": true,
-                                  "format": "uri",
-                                  "example": "https://api.github.com/licenses/mit"
-                                },
-                                "spdx_id": {
-                                  "type": "string",
-                                  "nullable": true,
-                                  "example": "MIT"
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDc6TGljZW5zZW1pdA=="
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri"
-                                }
-                              },
-                              "required": [
-                                "key",
-                                "name",
-                                "url",
-                                "spdx_id",
-                                "node_id"
-                              ],
-                              "nullable": true
-                            },
-                            "organization": {
-                              "title": "Simple User",
-                              "description": "Simple User",
-                              "type": "object",
-                              "properties": {
-                                "name": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "email": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "login": {
-                                  "type": "string",
-                                  "example": "octocat"
-                                },
-                                "id": {
-                                  "type": "integer",
-                                  "example": 1
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDQ6VXNlcjE="
-                                },
-                                "avatar_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/images/error/octocat_happy.gif"
-                                },
-                                "gravatar_id": {
-                                  "type": "string",
-                                  "example": "41d064eb2195891e12d0413f63227ea7",
-                                  "nullable": true
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat"
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/octocat"
-                                },
-                                "followers_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/followers"
-                                },
-                                "following_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/following{/other_user}"
-                                },
-                                "gists_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                                },
-                                "starred_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                                },
-                                "subscriptions_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/subscriptions"
-                                },
-                                "organizations_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/orgs"
-                                },
-                                "repos_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/repos"
-                                },
-                                "events_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/events{/privacy}"
-                                },
-                                "received_events_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/received_events"
-                                },
-                                "type": {
-                                  "type": "string",
-                                  "example": "User"
-                                },
-                                "site_admin": {
-                                  "type": "boolean"
-                                },
-                                "starred_at": {
-                                  "type": "string",
-                                  "example": "\"2020-07-09T00:17:55Z\""
-                                }
-                              },
-                              "required": [
-                                "avatar_url",
-                                "events_url",
-                                "followers_url",
-                                "following_url",
-                                "gists_url",
-                                "gravatar_id",
-                                "html_url",
-                                "id",
-                                "node_id",
-                                "login",
-                                "organizations_url",
-                                "received_events_url",
-                                "repos_url",
-                                "site_admin",
-                                "starred_url",
-                                "subscriptions_url",
-                                "type",
-                                "url"
-                              ],
-                              "nullable": true
-                            },
-                            "forks": {
-                              "type": "integer"
-                            },
-                            "permissions": {
-                              "type": "object",
-                              "properties": {
-                                "admin": {
-                                  "type": "boolean"
-                                },
-                                "pull": {
-                                  "type": "boolean"
-                                },
-                                "triage": {
-                                  "type": "boolean"
-                                },
-                                "push": {
-                                  "type": "boolean"
-                                },
-                                "maintain": {
-                                  "type": "boolean"
-                                }
-                              },
-                              "required": [
-                                "admin",
-                                "pull",
-                                "push"
-                              ]
-                            },
-                            "owner": {
-                              "title": "Simple User",
-                              "description": "Simple User",
-                              "type": "object",
-                              "properties": {
-                                "name": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "email": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "login": {
-                                  "type": "string",
-                                  "example": "octocat"
-                                },
-                                "id": {
-                                  "type": "integer",
-                                  "example": 1
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDQ6VXNlcjE="
-                                },
-                                "avatar_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/images/error/octocat_happy.gif"
-                                },
-                                "gravatar_id": {
-                                  "type": "string",
-                                  "example": "41d064eb2195891e12d0413f63227ea7",
-                                  "nullable": true
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat"
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/octocat"
-                                },
-                                "followers_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/followers"
-                                },
-                                "following_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/following{/other_user}"
-                                },
-                                "gists_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                                },
-                                "starred_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                                },
-                                "subscriptions_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/subscriptions"
-                                },
-                                "organizations_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/orgs"
-                                },
-                                "repos_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/repos"
-                                },
-                                "events_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/events{/privacy}"
-                                },
-                                "received_events_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/received_events"
-                                },
-                                "type": {
-                                  "type": "string",
-                                  "example": "User"
-                                },
-                                "site_admin": {
-                                  "type": "boolean"
-                                },
-                                "starred_at": {
-                                  "type": "string",
-                                  "example": "\"2020-07-09T00:17:55Z\""
-                                }
-                              },
-                              "required": [
-                                "avatar_url",
-                                "events_url",
-                                "followers_url",
-                                "following_url",
-                                "gists_url",
-                                "gravatar_id",
-                                "html_url",
-                                "id",
-                                "node_id",
-                                "login",
-                                "organizations_url",
-                                "received_events_url",
-                                "repos_url",
-                                "site_admin",
-                                "starred_url",
-                                "subscriptions_url",
-                                "type",
-                                "url"
-                              ]
-                            },
-                            "private": {
-                              "description": "Whether the repository is private or public.",
-                              "default": false,
-                              "type": "boolean"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/octocat/Hello-World"
-                            },
-                            "description": {
-                              "type": "string",
-                              "example": "This your first repo!",
-                              "nullable": true
-                            },
-                            "fork": {
-                              "type": "boolean"
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/repos/octocat/Hello-World"
-                            },
-                            "archive_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
-                            },
-                            "assignees_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
-                            },
-                            "blobs_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
-                            },
-                            "branches_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
-                            },
-                            "collaborators_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
-                            },
-                            "comments_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
-                            },
-                            "commits_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
-                            },
-                            "compare_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
-                            },
-                            "contents_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
-                            },
-                            "contributors_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
-                            },
-                            "deployments_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
-                            },
-                            "downloads_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
-                            },
-                            "events_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/events"
-                            },
-                            "forks_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/forks"
-                            },
-                            "git_commits_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
-                            },
-                            "git_refs_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
-                            },
-                            "git_tags_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
-                            },
-                            "git_url": {
-                              "type": "string",
-                              "example": "git:github.com/octocat/Hello-World.git"
-                            },
-                            "issue_comment_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
-                            },
-                            "issue_events_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
-                            },
-                            "issues_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
-                            },
-                            "keys_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
-                            },
-                            "labels_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
-                            },
-                            "languages_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/languages"
-                            },
-                            "merges_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/merges"
-                            },
-                            "milestones_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
-                            },
-                            "notifications_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
-                            },
-                            "pulls_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
-                            },
-                            "releases_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
-                            },
-                            "ssh_url": {
-                              "type": "string",
-                              "example": "git@github.com:octocat/Hello-World.git"
-                            },
-                            "stargazers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
-                            },
-                            "statuses_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
-                            },
-                            "subscribers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
-                            },
-                            "subscription_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
-                            },
-                            "tags_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/tags"
-                            },
-                            "teams_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/teams"
-                            },
-                            "trees_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
-                            },
-                            "clone_url": {
-                              "type": "string",
-                              "example": "https://github.com/octocat/Hello-World.git"
-                            },
-                            "mirror_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "git:git.example.com/octocat/Hello-World",
-                              "nullable": true
-                            },
-                            "hooks_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
-                            },
-                            "svn_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://svn.github.com/octocat/Hello-World"
-                            },
-                            "homepage": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com",
-                              "nullable": true
-                            },
-                            "language": {
-                              "type": "string",
-                              "nullable": true
-                            },
-                            "forks_count": {
-                              "type": "integer",
-                              "example": 9
-                            },
-                            "stargazers_count": {
-                              "type": "integer",
-                              "example": 80
-                            },
-                            "watchers_count": {
-                              "type": "integer",
-                              "example": 80
-                            },
-                            "size": {
-                              "type": "integer",
-                              "example": 108
-                            },
-                            "default_branch": {
-                              "description": "The default branch of the repository.",
-                              "type": "string",
-                              "example": "master"
-                            },
-                            "open_issues_count": {
-                              "type": "integer",
-                              "example": 0
-                            },
-                            "is_template": {
-                              "description": "Whether this repository acts as a template that can be used to generate new repositories.",
-                              "default": false,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "topics": {
-                              "type": "array",
-                              "items": {
-                                "type": "string"
-                              }
-                            },
-                            "has_issues": {
-                              "description": "Whether issues are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_projects": {
-                              "description": "Whether projects are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_wiki": {
-                              "description": "Whether the wiki is enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_pages": {
-                              "type": "boolean"
-                            },
-                            "has_downloads": {
-                              "description": "Whether downloads are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "archived": {
-                              "description": "Whether the repository is archived.",
-                              "default": false,
-                              "type": "boolean"
-                            },
-                            "disabled": {
-                              "type": "boolean",
-                              "description": "Returns whether or not this repository disabled."
-                            },
-                            "visibility": {
-                              "description": "The repository visibility: public, private, or internal.",
-                              "default": "public",
-                              "type": "string"
-                            },
-                            "pushed_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:06:43Z",
-                              "nullable": true
-                            },
-                            "created_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:01:12Z",
-                              "nullable": true
-                            },
-                            "updated_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:14:43Z",
-                              "nullable": true
-                            },
-                            "allow_rebase_merge": {
-                              "description": "Whether to allow rebase merges for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "template_repository": {
-                              "nullable": true,
-                              "type": "object",
-                              "properties": {
-                                "id": {
-                                  "type": "integer"
-                                },
-                                "node_id": {
-                                  "type": "string"
-                                },
-                                "name": {
-                                  "type": "string"
-                                },
-                                "full_name": {
-                                  "type": "string"
-                                },
-                                "owner": {
-                                  "type": "object",
-                                  "properties": {
-                                    "login": {
-                                      "type": "string"
-                                    },
-                                    "id": {
-                                      "type": "integer"
-                                    },
-                                    "node_id": {
-                                      "type": "string"
-                                    },
-                                    "avatar_url": {
-                                      "type": "string"
-                                    },
-                                    "gravatar_id": {
-                                      "type": "string"
-                                    },
-                                    "url": {
-                                      "type": "string"
-                                    },
-                                    "html_url": {
-                                      "type": "string"
-                                    },
-                                    "followers_url": {
-                                      "type": "string"
-                                    },
-                                    "following_url": {
-                                      "type": "string"
-                                    },
-                                    "gists_url": {
-                                      "type": "string"
-                                    },
-                                    "starred_url": {
-                                      "type": "string"
-                                    },
-                                    "subscriptions_url": {
-                                      "type": "string"
-                                    },
-                                    "organizations_url": {
-                                      "type": "string"
-                                    },
-                                    "repos_url": {
-                                      "type": "string"
-                                    },
-                                    "events_url": {
-                                      "type": "string"
-                                    },
-                                    "received_events_url": {
-                                      "type": "string"
-                                    },
-                                    "type": {
-                                      "type": "string"
-                                    },
-                                    "site_admin": {
-                                      "type": "boolean"
-                                    }
-                                  }
-                                },
-                                "private": {
-                                  "type": "boolean"
-                                },
-                                "html_url": {
-                                  "type": "string"
-                                },
-                                "description": {
-                                  "type": "string"
-                                },
-                                "fork": {
-                                  "type": "boolean"
-                                },
-                                "url": {
-                                  "type": "string"
-                                },
-                                "archive_url": {
-                                  "type": "string"
-                                },
-                                "assignees_url": {
-                                  "type": "string"
-                                },
-                                "blobs_url": {
-                                  "type": "string"
-                                },
-                                "branches_url": {
-                                  "type": "string"
-                                },
-                                "collaborators_url": {
-                                  "type": "string"
-                                },
-                                "comments_url": {
-                                  "type": "string"
-                                },
-                                "commits_url": {
-                                  "type": "string"
-                                },
-                                "compare_url": {
-                                  "type": "string"
-                                },
-                                "contents_url": {
-                                  "type": "string"
-                                },
-                                "contributors_url": {
-                                  "type": "string"
-                                },
-                                "deployments_url": {
-                                  "type": "string"
-                                },
-                                "downloads_url": {
-                                  "type": "string"
-                                },
-                                "events_url": {
-                                  "type": "string"
-                                },
-                                "forks_url": {
-                                  "type": "string"
-                                },
-                                "git_commits_url": {
-                                  "type": "string"
-                                },
-                                "git_refs_url": {
-                                  "type": "string"
-                                },
-                                "git_tags_url": {
-                                  "type": "string"
-                                },
-                                "git_url": {
-                                  "type": "string"
-                                },
-                                "issue_comment_url": {
-                                  "type": "string"
-                                },
-                                "issue_events_url": {
-                                  "type": "string"
-                                },
-                                "issues_url": {
-                                  "type": "string"
-                                },
-                                "keys_url": {
-                                  "type": "string"
-                                },
-                                "labels_url": {
-                                  "type": "string"
-                                },
-                                "languages_url": {
-                                  "type": "string"
-                                },
-                                "merges_url": {
-                                  "type": "string"
-                                },
-                                "milestones_url": {
-                                  "type": "string"
-                                },
-                                "notifications_url": {
-                                  "type": "string"
-                                },
-                                "pulls_url": {
-                                  "type": "string"
-                                },
-                                "releases_url": {
-                                  "type": "string"
-                                },
-                                "ssh_url": {
-                                  "type": "string"
-                                },
-                                "stargazers_url": {
-                                  "type": "string"
-                                },
-                                "statuses_url": {
-                                  "type": "string"
-                                },
-                                "subscribers_url": {
-                                  "type": "string"
-                                },
-                                "subscription_url": {
-                                  "type": "string"
-                                },
-                                "tags_url": {
-                                  "type": "string"
-                                },
-                                "teams_url": {
-                                  "type": "string"
-                                },
-                                "trees_url": {
-                                  "type": "string"
-                                },
-                                "clone_url": {
-                                  "type": "string"
-                                },
-                                "mirror_url": {
-                                  "type": "string"
-                                },
-                                "hooks_url": {
-                                  "type": "string"
-                                },
-                                "svn_url": {
-                                  "type": "string"
-                                },
-                                "homepage": {
-                                  "type": "string"
-                                },
-                                "language": {
-                                  "type": "string"
-                                },
-                                "forks_count": {
-                                  "type": "integer"
-                                },
-                                "stargazers_count": {
-                                  "type": "integer"
-                                },
-                                "watchers_count": {
-                                  "type": "integer"
-                                },
-                                "size": {
-                                  "type": "integer"
-                                },
-                                "default_branch": {
-                                  "type": "string"
-                                },
-                                "open_issues_count": {
-                                  "type": "integer"
-                                },
-                                "is_template": {
-                                  "type": "boolean"
-                                },
-                                "topics": {
-                                  "type": "array",
-                                  "items": {
-                                    "type": "string"
-                                  }
-                                },
-                                "has_issues": {
-                                  "type": "boolean"
-                                },
-                                "has_projects": {
-                                  "type": "boolean"
-                                },
-                                "has_wiki": {
-                                  "type": "boolean"
-                                },
-                                "has_pages": {
-                                  "type": "boolean"
-                                },
-                                "has_downloads": {
-                                  "type": "boolean"
-                                },
-                                "archived": {
-                                  "type": "boolean"
-                                },
-                                "disabled": {
-                                  "type": "boolean"
-                                },
-                                "visibility": {
-                                  "type": "string"
-                                },
-                                "pushed_at": {
-                                  "type": "string"
-                                },
-                                "created_at": {
-                                  "type": "string"
-                                },
-                                "updated_at": {
-                                  "type": "string"
-                                },
-                                "permissions": {
-                                  "type": "object",
-                                  "properties": {
-                                    "admin": {
-                                      "type": "boolean"
-                                    },
-                                    "maintain": {
-                                      "type": "boolean"
-                                    },
-                                    "push": {
-                                      "type": "boolean"
-                                    },
-                                    "triage": {
-                                      "type": "boolean"
-                                    },
-                                    "pull": {
-                                      "type": "boolean"
-                                    }
-                                  }
-                                },
-                                "allow_rebase_merge": {
-                                  "type": "boolean"
-                                },
-                                "temp_clone_token": {
-                                  "type": "string"
-                                },
-                                "allow_squash_merge": {
-                                  "type": "boolean"
-                                },
-                                "allow_auto_merge": {
-                                  "type": "boolean"
-                                },
-                                "delete_branch_on_merge": {
-                                  "type": "boolean"
-                                },
-                                "allow_update_branch": {
-                                  "type": "boolean"
-                                },
-                                "allow_merge_commit": {
-                                  "type": "boolean"
-                                },
-                                "subscribers_count": {
-                                  "type": "integer"
-                                },
-                                "network_count": {
-                                  "type": "integer"
-                                }
-                              }
-                            },
-                            "temp_clone_token": {
-                              "type": "string"
-                            },
-                            "allow_squash_merge": {
-                              "description": "Whether to allow squash merges for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "allow_auto_merge": {
-                              "description": "Whether to allow Auto-merge to be used on pull requests.",
-                              "default": false,
-                              "type": "boolean",
-                              "example": false
-                            },
-                            "delete_branch_on_merge": {
-                              "description": "Whether to delete head branches when pull requests are merged",
-                              "default": false,
-                              "type": "boolean",
-                              "example": false
-                            },
-                            "allow_merge_commit": {
-                              "description": "Whether to allow merge commits for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "allow_forking": {
-                              "description": "Whether to allow forking this repo",
-                              "type": "boolean"
-                            },
-                            "subscribers_count": {
-                              "type": "integer"
-                            },
-                            "network_count": {
-                              "type": "integer"
-                            },
-                            "open_issues": {
-                              "type": "integer"
-                            },
-                            "watchers": {
-                              "type": "integer"
-                            },
-                            "master_branch": {
-                              "type": "string"
-                            },
-                            "starred_at": {
-                              "type": "string",
-                              "example": "\"2020-07-09T00:17:42Z\""
-                            }
-                          },
-                          "required": [
-                            "archive_url",
-                            "assignees_url",
-                            "blobs_url",
-                            "branches_url",
-                            "collaborators_url",
-                            "comments_url",
-                            "commits_url",
-                            "compare_url",
-                            "contents_url",
-                            "contributors_url",
-                            "deployments_url",
-                            "description",
-                            "downloads_url",
-                            "events_url",
-                            "fork",
-                            "forks_url",
-                            "full_name",
-                            "git_commits_url",
-                            "git_refs_url",
-                            "git_tags_url",
-                            "hooks_url",
-                            "html_url",
-                            "id",
-                            "node_id",
-                            "issue_comment_url",
-                            "issue_events_url",
-                            "issues_url",
-                            "keys_url",
-                            "labels_url",
-                            "languages_url",
-                            "merges_url",
-                            "milestones_url",
-                            "name",
-                            "notifications_url",
-                            "owner",
-                            "private",
-                            "pulls_url",
-                            "releases_url",
-                            "stargazers_url",
-                            "statuses_url",
-                            "subscribers_url",
-                            "subscription_url",
-                            "tags_url",
-                            "teams_url",
-                            "trees_url",
-                            "url",
-                            "clone_url",
-                            "default_branch",
-                            "forks",
-                            "forks_count",
-                            "git_url",
-                            "has_downloads",
-                            "has_issues",
-                            "has_projects",
-                            "has_wiki",
-                            "has_pages",
-                            "homepage",
-                            "language",
-                            "archived",
-                            "disabled",
-                            "mirror_url",
-                            "open_issues",
-                            "open_issues_count",
-                            "license",
-                            "pushed_at",
-                            "size",
-                            "ssh_url",
-                            "stargazers_count",
-                            "svn_url",
-                            "watchers",
-                            "watchers_count",
-                            "created_at",
-                            "updated_at"
-                          ],
-                          "nullable": true
-                        },
-                        "temp_clone_token": {
-                          "type": "string"
-                        },
-                        "delete_branch_on_merge": {
-                          "type": "boolean"
-                        },
-                        "subscribers_count": {
-                          "type": "integer"
-                        },
-                        "network_count": {
-                          "type": "integer"
-                        },
-                        "code_of_conduct": {
-                          "title": "Code Of Conduct",
-                          "description": "Code Of Conduct",
-                          "type": "object",
-                          "properties": {
-                            "key": {
-                              "type": "string",
-                              "example": "contributor_covenant"
-                            },
-                            "name": {
-                              "type": "string",
-                              "example": "Contributor Covenant"
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/codes_of_conduct/contributor_covenant"
-                            },
-                            "body": {
-                              "type": "string",
-                              "example": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.\n\n## Our Standards\n\nExamples of behavior that contributes to creating a positive environment include:\n\n* Using welcoming and inclusive language\n* Being respectful of differing viewpoints and experiences\n* Gracefully accepting constructive criticism\n* Focusing on what is best for the community\n* Showing empathy towards other community members\n\nExamples of unacceptable behavior by participants include:\n\n* The use of sexualized language or imagery and unwelcome sexual attention or advances\n* Trolling, insulting/derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or electronic address, without explicit permission\n* Other conduct which could reasonably be considered inappropriate in a professional setting\n\n## Our Responsibilities\n\nProject maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response\n                  to any instances of unacceptable behavior.\n\nProject maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.\n\n## Scope\n\nThis Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address,\n                  posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [EMAIL]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.\n\nProject maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]\n\n[homepage]: http://contributor-covenant.org\n[version]: http://contributor-covenant.org/version/1/4/\n"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "nullable": true
-                            }
-                          },
-                          "required": [
-                            "url",
-                            "html_url",
-                            "key",
-                            "name"
-                          ]
-                        },
-                        "license": {
-                          "type": "object",
-                          "properties": {
-                            "key": {
-                              "type": "string"
-                            },
-                            "name": {
-                              "type": "string"
-                            },
-                            "spdx_id": {
-                              "type": "string"
-                            },
-                            "url": {
-                              "type": "string"
-                            },
-                            "node_id": {
-                              "type": "string"
-                            }
-                          },
-                          "nullable": true
-                        },
-                        "forks": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "open_issues": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "watchers": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "allow_forking": {
-                          "type": "boolean"
-                        }
-                      },
-                      "required": [
-                        "archive_url",
-                        "assignees_url",
-                        "blobs_url",
-                        "branches_url",
-                        "collaborators_url",
-                        "comments_url",
-                        "commits_url",
-                        "compare_url",
-                        "contents_url",
-                        "contributors_url",
-                        "deployments_url",
-                        "description",
-                        "downloads_url",
-                        "events_url",
-                        "fork",
-                        "forks_url",
-                        "full_name",
-                        "git_commits_url",
-                        "git_refs_url",
-                        "git_tags_url",
-                        "hooks_url",
-                        "html_url",
-                        "id",
-                        "node_id",
-                        "issue_comment_url",
-                        "issue_events_url",
-                        "issues_url",
-                        "keys_url",
-                        "labels_url",
-                        "languages_url",
-                        "merges_url",
-                        "milestones_url",
-                        "name",
-                        "notifications_url",
-                        "owner",
-                        "private",
-                        "pulls_url",
-                        "releases_url",
-                        "stargazers_url",
-                        "statuses_url",
-                        "subscribers_url",
-                        "subscription_url",
-                        "tags_url",
-                        "teams_url",
-                        "trees_url",
-                        "url"
-                      ]
-                    },
-                    "head_repository": {
-                      "title": "Minimal Repository",
-                      "description": "Minimal Repository",
-                      "type": "object",
-                      "properties": {
-                        "id": {
-                          "type": "integer",
-                          "example": 1296269
-                        },
-                        "node_id": {
-                          "type": "string",
-                          "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
-                        },
-                        "name": {
-                          "type": "string",
-                          "example": "Hello-World"
-                        },
-                        "full_name": {
-                          "type": "string",
-                          "example": "octocat/Hello-World"
-                        },
-                        "owner": {
-                          "title": "Simple User",
-                          "description": "Simple User",
-                          "type": "object",
-                          "properties": {
-                            "name": {
-                              "nullable": true,
-                              "type": "string"
-                            },
-                            "email": {
-                              "nullable": true,
-                              "type": "string"
-                            },
-                            "login": {
-                              "type": "string",
-                              "example": "octocat"
-                            },
-                            "id": {
-                              "type": "integer",
-                              "example": 1
-                            },
-                            "node_id": {
-                              "type": "string",
-                              "example": "MDQ6VXNlcjE="
-                            },
-                            "avatar_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/images/error/octocat_happy.gif"
-                            },
-                            "gravatar_id": {
-                              "type": "string",
-                              "example": "41d064eb2195891e12d0413f63227ea7",
-                              "nullable": true
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/octocat"
-                            },
-                            "followers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/followers"
-                            },
-                            "following_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/following{/other_user}"
-                            },
-                            "gists_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                            },
-                            "starred_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                            },
-                            "subscriptions_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/subscriptions"
-                            },
-                            "organizations_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/orgs"
-                            },
-                            "repos_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/repos"
-                            },
-                            "events_url": {
-                              "type": "string",
-                              "example": "https://api.github.com/users/octocat/events{/privacy}"
-                            },
-                            "received_events_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/users/octocat/received_events"
-                            },
-                            "type": {
-                              "type": "string",
-                              "example": "User"
-                            },
-                            "site_admin": {
-                              "type": "boolean"
-                            },
-                            "starred_at": {
-                              "type": "string",
-                              "example": "\"2020-07-09T00:17:55Z\""
-                            }
-                          },
-                          "required": [
-                            "avatar_url",
-                            "events_url",
-                            "followers_url",
-                            "following_url",
-                            "gists_url",
-                            "gravatar_id",
-                            "html_url",
-                            "id",
-                            "node_id",
-                            "login",
-                            "organizations_url",
-                            "received_events_url",
-                            "repos_url",
-                            "site_admin",
-                            "starred_url",
-                            "subscriptions_url",
-                            "type",
-                            "url"
-                          ]
-                        },
-                        "private": {
-                          "type": "boolean"
-                        },
-                        "html_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "https://github.com/octocat/Hello-World"
-                        },
-                        "description": {
-                          "type": "string",
-                          "example": "This your first repo!",
-                          "nullable": true
-                        },
-                        "fork": {
-                          "type": "boolean"
-                        },
-                        "url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "https://api.github.com/repos/octocat/Hello-World"
-                        },
-                        "archive_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
-                        },
-                        "assignees_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
-                        },
-                        "blobs_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
-                        },
-                        "branches_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
-                        },
-                        "collaborators_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
-                        },
-                        "comments_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
-                        },
-                        "commits_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
-                        },
-                        "compare_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
-                        },
-                        "contents_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
-                        },
-                        "contributors_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
-                        },
-                        "deployments_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
-                        },
-                        "downloads_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
-                        },
-                        "events_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/events"
-                        },
-                        "forks_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/forks"
-                        },
-                        "git_commits_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
-                        },
-                        "git_refs_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
-                        },
-                        "git_tags_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
-                        },
-                        "git_url": {
-                          "type": "string"
-                        },
-                        "issue_comment_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
-                        },
-                        "issue_events_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
-                        },
-                        "issues_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
-                        },
-                        "keys_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
-                        },
-                        "labels_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
-                        },
-                        "languages_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/languages"
-                        },
-                        "merges_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/merges"
-                        },
-                        "milestones_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
-                        },
-                        "notifications_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
-                        },
-                        "pulls_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
-                        },
-                        "releases_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
-                        },
-                        "ssh_url": {
-                          "type": "string"
-                        },
-                        "stargazers_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
-                        },
-                        "statuses_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
-                        },
-                        "subscribers_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
-                        },
-                        "subscription_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
-                        },
-                        "tags_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/tags"
-                        },
-                        "teams_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/teams"
-                        },
-                        "trees_url": {
-                          "type": "string",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
-                        },
-                        "clone_url": {
-                          "type": "string"
-                        },
-                        "mirror_url": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "hooks_url": {
-                          "type": "string",
-                          "format": "uri",
-                          "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
-                        },
-                        "svn_url": {
-                          "type": "string"
-                        },
-                        "homepage": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "language": {
-                          "type": "string",
-                          "nullable": true
-                        },
-                        "forks_count": {
-                          "type": "integer"
-                        },
-                        "stargazers_count": {
-                          "type": "integer"
-                        },
-                        "watchers_count": {
-                          "type": "integer"
-                        },
-                        "size": {
-                          "type": "integer"
-                        },
-                        "default_branch": {
-                          "type": "string"
-                        },
-                        "open_issues_count": {
-                          "type": "integer"
-                        },
-                        "is_template": {
-                          "type": "boolean"
-                        },
-                        "topics": {
-                          "type": "array",
-                          "items": {
-                            "type": "string"
-                          }
-                        },
-                        "has_issues": {
-                          "type": "boolean"
-                        },
-                        "has_projects": {
-                          "type": "boolean"
-                        },
-                        "has_wiki": {
-                          "type": "boolean"
-                        },
-                        "has_pages": {
-                          "type": "boolean"
-                        },
-                        "has_downloads": {
-                          "type": "boolean"
-                        },
-                        "archived": {
-                          "type": "boolean"
-                        },
-                        "disabled": {
-                          "type": "boolean"
-                        },
-                        "visibility": {
-                          "type": "string"
-                        },
-                        "pushed_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:06:43Z",
-                          "nullable": true
-                        },
-                        "created_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:01:12Z",
-                          "nullable": true
-                        },
-                        "updated_at": {
-                          "type": "string",
-                          "format": "date-time",
-                          "example": "2011-01-26T19:14:43Z",
-                          "nullable": true
-                        },
-                        "permissions": {
-                          "type": "object",
-                          "properties": {
-                            "admin": {
-                              "type": "boolean"
-                            },
-                            "maintain": {
-                              "type": "boolean"
-                            },
-                            "push": {
-                              "type": "boolean"
-                            },
-                            "triage": {
-                              "type": "boolean"
-                            },
-                            "pull": {
-                              "type": "boolean"
-                            }
-                          }
-                        },
-                        "template_repository": {
-                          "title": "Repository",
-                          "description": "A git repository",
-                          "type": "object",
-                          "properties": {
-                            "id": {
-                              "description": "Unique identifier of the repository",
-                              "example": 42,
-                              "type": "integer"
-                            },
-                            "node_id": {
-                              "type": "string",
-                              "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
-                            },
-                            "name": {
-                              "description": "The name of the repository.",
-                              "type": "string",
-                              "example": "Team Environment"
-                            },
-                            "full_name": {
-                              "type": "string",
-                              "example": "octocat/Hello-World"
-                            },
-                            "license": {
-                              "title": "License Simple",
-                              "description": "License Simple",
-                              "type": "object",
-                              "properties": {
-                                "key": {
-                                  "type": "string",
-                                  "example": "mit"
-                                },
-                                "name": {
-                                  "type": "string",
-                                  "example": "MIT License"
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "nullable": true,
-                                  "format": "uri",
-                                  "example": "https://api.github.com/licenses/mit"
-                                },
-                                "spdx_id": {
-                                  "type": "string",
-                                  "nullable": true,
-                                  "example": "MIT"
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDc6TGljZW5zZW1pdA=="
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri"
-                                }
-                              },
-                              "required": [
-                                "key",
-                                "name",
-                                "url",
-                                "spdx_id",
-                                "node_id"
-                              ],
-                              "nullable": true
-                            },
-                            "organization": {
-                              "title": "Simple User",
-                              "description": "Simple User",
-                              "type": "object",
-                              "properties": {
-                                "name": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "email": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "login": {
-                                  "type": "string",
-                                  "example": "octocat"
-                                },
-                                "id": {
-                                  "type": "integer",
-                                  "example": 1
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDQ6VXNlcjE="
-                                },
-                                "avatar_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/images/error/octocat_happy.gif"
-                                },
-                                "gravatar_id": {
-                                  "type": "string",
-                                  "example": "41d064eb2195891e12d0413f63227ea7",
-                                  "nullable": true
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat"
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/octocat"
-                                },
-                                "followers_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/followers"
-                                },
-                                "following_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/following{/other_user}"
-                                },
-                                "gists_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                                },
-                                "starred_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                                },
-                                "subscriptions_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/subscriptions"
-                                },
-                                "organizations_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/orgs"
-                                },
-                                "repos_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/repos"
-                                },
-                                "events_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/events{/privacy}"
-                                },
-                                "received_events_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/received_events"
-                                },
-                                "type": {
-                                  "type": "string",
-                                  "example": "User"
-                                },
-                                "site_admin": {
-                                  "type": "boolean"
-                                },
-                                "starred_at": {
-                                  "type": "string",
-                                  "example": "\"2020-07-09T00:17:55Z\""
-                                }
-                              },
-                              "required": [
-                                "avatar_url",
-                                "events_url",
-                                "followers_url",
-                                "following_url",
-                                "gists_url",
-                                "gravatar_id",
-                                "html_url",
-                                "id",
-                                "node_id",
-                                "login",
-                                "organizations_url",
-                                "received_events_url",
-                                "repos_url",
-                                "site_admin",
-                                "starred_url",
-                                "subscriptions_url",
-                                "type",
-                                "url"
-                              ],
-                              "nullable": true
-                            },
-                            "forks": {
-                              "type": "integer"
-                            },
-                            "permissions": {
-                              "type": "object",
-                              "properties": {
-                                "admin": {
-                                  "type": "boolean"
-                                },
-                                "pull": {
-                                  "type": "boolean"
-                                },
-                                "triage": {
-                                  "type": "boolean"
-                                },
-                                "push": {
-                                  "type": "boolean"
-                                },
-                                "maintain": {
-                                  "type": "boolean"
-                                }
-                              },
-                              "required": [
-                                "admin",
-                                "pull",
-                                "push"
-                              ]
-                            },
-                            "owner": {
-                              "title": "Simple User",
-                              "description": "Simple User",
-                              "type": "object",
-                              "properties": {
-                                "name": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "email": {
-                                  "nullable": true,
-                                  "type": "string"
-                                },
-                                "login": {
-                                  "type": "string",
-                                  "example": "octocat"
-                                },
-                                "id": {
-                                  "type": "integer",
-                                  "example": 1
-                                },
-                                "node_id": {
-                                  "type": "string",
-                                  "example": "MDQ6VXNlcjE="
-                                },
-                                "avatar_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/images/error/octocat_happy.gif"
-                                },
-                                "gravatar_id": {
-                                  "type": "string",
-                                  "example": "41d064eb2195891e12d0413f63227ea7",
-                                  "nullable": true
-                                },
-                                "url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat"
-                                },
-                                "html_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://github.com/octocat"
-                                },
-                                "followers_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/followers"
-                                },
-                                "following_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/following{/other_user}"
-                                },
-                                "gists_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/gists{/gist_id}"
-                                },
-                                "starred_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
-                                },
-                                "subscriptions_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/subscriptions"
-                                },
-                                "organizations_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/orgs"
-                                },
-                                "repos_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/repos"
-                                },
-                                "events_url": {
-                                  "type": "string",
-                                  "example": "https://api.github.com/users/octocat/events{/privacy}"
-                                },
-                                "received_events_url": {
-                                  "type": "string",
-                                  "format": "uri",
-                                  "example": "https://api.github.com/users/octocat/received_events"
-                                },
-                                "type": {
-                                  "type": "string",
-                                  "example": "User"
-                                },
-                                "site_admin": {
-                                  "type": "boolean"
-                                },
-                                "starred_at": {
-                                  "type": "string",
-                                  "example": "\"2020-07-09T00:17:55Z\""
-                                }
-                              },
-                              "required": [
-                                "avatar_url",
-                                "events_url",
-                                "followers_url",
-                                "following_url",
-                                "gists_url",
-                                "gravatar_id",
-                                "html_url",
-                                "id",
-                                "node_id",
-                                "login",
-                                "organizations_url",
-                                "received_events_url",
-                                "repos_url",
-                                "site_admin",
-                                "starred_url",
-                                "subscriptions_url",
-                                "type",
-                                "url"
-                              ]
-                            },
-                            "private": {
-                              "description": "Whether the repository is private or public.",
-                              "default": false,
-                              "type": "boolean"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com/octocat/Hello-World"
-                            },
-                            "description": {
-                              "type": "string",
-                              "example": "This your first repo!",
-                              "nullable": true
-                            },
-                            "fork": {
-                              "type": "boolean"
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/repos/octocat/Hello-World"
-                            },
-                            "archive_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
-                            },
-                            "assignees_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
-                            },
-                            "blobs_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
-                            },
-                            "branches_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
-                            },
-                            "collaborators_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
-                            },
-                            "comments_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
-                            },
-                            "commits_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
-                            },
-                            "compare_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
-                            },
-                            "contents_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
-                            },
-                            "contributors_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
-                            },
-                            "deployments_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
-                            },
-                            "downloads_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
-                            },
-                            "events_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/events"
-                            },
-                            "forks_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/forks"
-                            },
-                            "git_commits_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
-                            },
-                            "git_refs_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
-                            },
-                            "git_tags_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
-                            },
-                            "git_url": {
-                              "type": "string",
-                              "example": "git:github.com/octocat/Hello-World.git"
-                            },
-                            "issue_comment_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
-                            },
-                            "issue_events_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
-                            },
-                            "issues_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
-                            },
-                            "keys_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
-                            },
-                            "labels_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
-                            },
-                            "languages_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/languages"
-                            },
-                            "merges_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/merges"
-                            },
-                            "milestones_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
-                            },
-                            "notifications_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
-                            },
-                            "pulls_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
-                            },
-                            "releases_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
-                            },
-                            "ssh_url": {
-                              "type": "string",
-                              "example": "git@github.com:octocat/Hello-World.git"
-                            },
-                            "stargazers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
-                            },
-                            "statuses_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
-                            },
-                            "subscribers_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
-                            },
-                            "subscription_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
-                            },
-                            "tags_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/tags"
-                            },
-                            "teams_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/teams"
-                            },
-                            "trees_url": {
-                              "type": "string",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
-                            },
-                            "clone_url": {
-                              "type": "string",
-                              "example": "https://github.com/octocat/Hello-World.git"
-                            },
-                            "mirror_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "git:git.example.com/octocat/Hello-World",
-                              "nullable": true
-                            },
-                            "hooks_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
-                            },
-                            "svn_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://svn.github.com/octocat/Hello-World"
-                            },
-                            "homepage": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://github.com",
-                              "nullable": true
-                            },
-                            "language": {
-                              "type": "string",
-                              "nullable": true
-                            },
-                            "forks_count": {
-                              "type": "integer",
-                              "example": 9
-                            },
-                            "stargazers_count": {
-                              "type": "integer",
-                              "example": 80
-                            },
-                            "watchers_count": {
-                              "type": "integer",
-                              "example": 80
-                            },
-                            "size": {
-                              "type": "integer",
-                              "example": 108
-                            },
-                            "default_branch": {
-                              "description": "The default branch of the repository.",
-                              "type": "string",
-                              "example": "master"
-                            },
-                            "open_issues_count": {
-                              "type": "integer",
-                              "example": 0
-                            },
-                            "is_template": {
-                              "description": "Whether this repository acts as a template that can be used to generate new repositories.",
-                              "default": false,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "topics": {
-                              "type": "array",
-                              "items": {
-                                "type": "string"
-                              }
-                            },
-                            "has_issues": {
-                              "description": "Whether issues are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_projects": {
-                              "description": "Whether projects are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_wiki": {
-                              "description": "Whether the wiki is enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "has_pages": {
-                              "type": "boolean"
-                            },
-                            "has_downloads": {
-                              "description": "Whether downloads are enabled.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "archived": {
-                              "description": "Whether the repository is archived.",
-                              "default": false,
-                              "type": "boolean"
-                            },
-                            "disabled": {
-                              "type": "boolean",
-                              "description": "Returns whether or not this repository disabled."
-                            },
-                            "visibility": {
-                              "description": "The repository visibility: public, private, or internal.",
-                              "default": "public",
-                              "type": "string"
-                            },
-                            "pushed_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:06:43Z",
-                              "nullable": true
-                            },
-                            "created_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:01:12Z",
-                              "nullable": true
-                            },
-                            "updated_at": {
-                              "type": "string",
-                              "format": "date-time",
-                              "example": "2011-01-26T19:14:43Z",
-                              "nullable": true
-                            },
-                            "allow_rebase_merge": {
-                              "description": "Whether to allow rebase merges for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "template_repository": {
-                              "nullable": true,
-                              "type": "object",
-                              "properties": {
-                                "id": {
-                                  "type": "integer"
-                                },
-                                "node_id": {
-                                  "type": "string"
-                                },
-                                "name": {
-                                  "type": "string"
-                                },
-                                "full_name": {
-                                  "type": "string"
-                                },
-                                "owner": {
-                                  "type": "object",
-                                  "properties": {
-                                    "login": {
-                                      "type": "string"
-                                    },
-                                    "id": {
-                                      "type": "integer"
-                                    },
-                                    "node_id": {
-                                      "type": "string"
-                                    },
-                                    "avatar_url": {
-                                      "type": "string"
-                                    },
-                                    "gravatar_id": {
-                                      "type": "string"
-                                    },
-                                    "url": {
-                                      "type": "string"
-                                    },
-                                    "html_url": {
-                                      "type": "string"
-                                    },
-                                    "followers_url": {
-                                      "type": "string"
-                                    },
-                                    "following_url": {
-                                      "type": "string"
-                                    },
-                                    "gists_url": {
-                                      "type": "string"
-                                    },
-                                    "starred_url": {
-                                      "type": "string"
-                                    },
-                                    "subscriptions_url": {
-                                      "type": "string"
-                                    },
-                                    "organizations_url": {
-                                      "type": "string"
-                                    },
-                                    "repos_url": {
-                                      "type": "string"
-                                    },
-                                    "events_url": {
-                                      "type": "string"
-                                    },
-                                    "received_events_url": {
-                                      "type": "string"
-                                    },
-                                    "type": {
-                                      "type": "string"
-                                    },
-                                    "site_admin": {
-                                      "type": "boolean"
-                                    }
-                                  }
-                                },
-                                "private": {
-                                  "type": "boolean"
-                                },
-                                "html_url": {
-                                  "type": "string"
-                                },
-                                "description": {
-                                  "type": "string"
-                                },
-                                "fork": {
-                                  "type": "boolean"
-                                },
-                                "url": {
-                                  "type": "string"
-                                },
-                                "archive_url": {
-                                  "type": "string"
-                                },
-                                "assignees_url": {
-                                  "type": "string"
-                                },
-                                "blobs_url": {
-                                  "type": "string"
-                                },
-                                "branches_url": {
-                                  "type": "string"
-                                },
-                                "collaborators_url": {
-                                  "type": "string"
-                                },
-                                "comments_url": {
-                                  "type": "string"
-                                },
-                                "commits_url": {
-                                  "type": "string"
-                                },
-                                "compare_url": {
-                                  "type": "string"
-                                },
-                                "contents_url": {
-                                  "type": "string"
-                                },
-                                "contributors_url": {
-                                  "type": "string"
-                                },
-                                "deployments_url": {
-                                  "type": "string"
-                                },
-                                "downloads_url": {
-                                  "type": "string"
-                                },
-                                "events_url": {
-                                  "type": "string"
-                                },
-                                "forks_url": {
-                                  "type": "string"
-                                },
-                                "git_commits_url": {
-                                  "type": "string"
-                                },
-                                "git_refs_url": {
-                                  "type": "string"
-                                },
-                                "git_tags_url": {
-                                  "type": "string"
-                                },
-                                "git_url": {
-                                  "type": "string"
-                                },
-                                "issue_comment_url": {
-                                  "type": "string"
-                                },
-                                "issue_events_url": {
-                                  "type": "string"
-                                },
-                                "issues_url": {
-                                  "type": "string"
-                                },
-                                "keys_url": {
-                                  "type": "string"
-                                },
-                                "labels_url": {
-                                  "type": "string"
-                                },
-                                "languages_url": {
-                                  "type": "string"
-                                },
-                                "merges_url": {
-                                  "type": "string"
-                                },
-                                "milestones_url": {
-                                  "type": "string"
-                                },
-                                "notifications_url": {
-                                  "type": "string"
-                                },
-                                "pulls_url": {
-                                  "type": "string"
-                                },
-                                "releases_url": {
-                                  "type": "string"
-                                },
-                                "ssh_url": {
-                                  "type": "string"
-                                },
-                                "stargazers_url": {
-                                  "type": "string"
-                                },
-                                "statuses_url": {
-                                  "type": "string"
-                                },
-                                "subscribers_url": {
-                                  "type": "string"
-                                },
-                                "subscription_url": {
-                                  "type": "string"
-                                },
-                                "tags_url": {
-                                  "type": "string"
-                                },
-                                "teams_url": {
-                                  "type": "string"
-                                },
-                                "trees_url": {
-                                  "type": "string"
-                                },
-                                "clone_url": {
-                                  "type": "string"
-                                },
-                                "mirror_url": {
-                                  "type": "string"
-                                },
-                                "hooks_url": {
-                                  "type": "string"
-                                },
-                                "svn_url": {
-                                  "type": "string"
-                                },
-                                "homepage": {
-                                  "type": "string"
-                                },
-                                "language": {
-                                  "type": "string"
-                                },
-                                "forks_count": {
-                                  "type": "integer"
-                                },
-                                "stargazers_count": {
-                                  "type": "integer"
-                                },
-                                "watchers_count": {
-                                  "type": "integer"
-                                },
-                                "size": {
-                                  "type": "integer"
-                                },
-                                "default_branch": {
-                                  "type": "string"
-                                },
-                                "open_issues_count": {
-                                  "type": "integer"
-                                },
-                                "is_template": {
-                                  "type": "boolean"
-                                },
-                                "topics": {
-                                  "type": "array",
-                                  "items": {
-                                    "type": "string"
-                                  }
-                                },
-                                "has_issues": {
-                                  "type": "boolean"
-                                },
-                                "has_projects": {
-                                  "type": "boolean"
-                                },
-                                "has_wiki": {
-                                  "type": "boolean"
-                                },
-                                "has_pages": {
-                                  "type": "boolean"
-                                },
-                                "has_downloads": {
-                                  "type": "boolean"
-                                },
-                                "archived": {
-                                  "type": "boolean"
-                                },
-                                "disabled": {
-                                  "type": "boolean"
-                                },
-                                "visibility": {
-                                  "type": "string"
-                                },
-                                "pushed_at": {
-                                  "type": "string"
-                                },
-                                "created_at": {
-                                  "type": "string"
-                                },
-                                "updated_at": {
-                                  "type": "string"
-                                },
-                                "permissions": {
-                                  "type": "object",
-                                  "properties": {
-                                    "admin": {
-                                      "type": "boolean"
-                                    },
-                                    "maintain": {
-                                      "type": "boolean"
-                                    },
-                                    "push": {
-                                      "type": "boolean"
-                                    },
-                                    "triage": {
-                                      "type": "boolean"
-                                    },
-                                    "pull": {
-                                      "type": "boolean"
-                                    }
-                                  }
-                                },
-                                "allow_rebase_merge": {
-                                  "type": "boolean"
-                                },
-                                "temp_clone_token": {
-                                  "type": "string"
-                                },
-                                "allow_squash_merge": {
-                                  "type": "boolean"
-                                },
-                                "allow_auto_merge": {
-                                  "type": "boolean"
-                                },
-                                "delete_branch_on_merge": {
-                                  "type": "boolean"
-                                },
-                                "allow_update_branch": {
-                                  "type": "boolean"
-                                },
-                                "allow_merge_commit": {
-                                  "type": "boolean"
-                                },
-                                "subscribers_count": {
-                                  "type": "integer"
-                                },
-                                "network_count": {
-                                  "type": "integer"
-                                }
-                              }
-                            },
-                            "temp_clone_token": {
-                              "type": "string"
-                            },
-                            "allow_squash_merge": {
-                              "description": "Whether to allow squash merges for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "allow_auto_merge": {
-                              "description": "Whether to allow Auto-merge to be used on pull requests.",
-                              "default": false,
-                              "type": "boolean",
-                              "example": false
-                            },
-                            "delete_branch_on_merge": {
-                              "description": "Whether to delete head branches when pull requests are merged",
-                              "default": false,
-                              "type": "boolean",
-                              "example": false
-                            },
-                            "allow_merge_commit": {
-                              "description": "Whether to allow merge commits for pull requests.",
-                              "default": true,
-                              "type": "boolean",
-                              "example": true
-                            },
-                            "allow_forking": {
-                              "description": "Whether to allow forking this repo",
-                              "type": "boolean"
-                            },
-                            "subscribers_count": {
-                              "type": "integer"
-                            },
-                            "network_count": {
-                              "type": "integer"
-                            },
-                            "open_issues": {
-                              "type": "integer"
-                            },
-                            "watchers": {
-                              "type": "integer"
-                            },
-                            "master_branch": {
-                              "type": "string"
-                            },
-                            "starred_at": {
-                              "type": "string",
-                              "example": "\"2020-07-09T00:17:42Z\""
-                            }
-                          },
-                          "required": [
-                            "archive_url",
-                            "assignees_url",
-                            "blobs_url",
-                            "branches_url",
-                            "collaborators_url",
-                            "comments_url",
-                            "commits_url",
-                            "compare_url",
-                            "contents_url",
-                            "contributors_url",
-                            "deployments_url",
-                            "description",
-                            "downloads_url",
-                            "events_url",
-                            "fork",
-                            "forks_url",
-                            "full_name",
-                            "git_commits_url",
-                            "git_refs_url",
-                            "git_tags_url",
-                            "hooks_url",
-                            "html_url",
-                            "id",
-                            "node_id",
-                            "issue_comment_url",
-                            "issue_events_url",
-                            "issues_url",
-                            "keys_url",
-                            "labels_url",
-                            "languages_url",
-                            "merges_url",
-                            "milestones_url",
-                            "name",
-                            "notifications_url",
-                            "owner",
-                            "private",
-                            "pulls_url",
-                            "releases_url",
-                            "stargazers_url",
-                            "statuses_url",
-                            "subscribers_url",
-                            "subscription_url",
-                            "tags_url",
-                            "teams_url",
-                            "trees_url",
-                            "url",
-                            "clone_url",
-                            "default_branch",
-                            "forks",
-                            "forks_count",
-                            "git_url",
-                            "has_downloads",
-                            "has_issues",
-                            "has_projects",
-                            "has_wiki",
-                            "has_pages",
-                            "homepage",
-                            "language",
-                            "archived",
-                            "disabled",
-                            "mirror_url",
-                            "open_issues",
-                            "open_issues_count",
-                            "license",
-                            "pushed_at",
-                            "size",
-                            "ssh_url",
-                            "stargazers_count",
-                            "svn_url",
-                            "watchers",
-                            "watchers_count",
-                            "created_at",
-                            "updated_at"
-                          ],
-                          "nullable": true
-                        },
-                        "temp_clone_token": {
-                          "type": "string"
-                        },
-                        "delete_branch_on_merge": {
-                          "type": "boolean"
-                        },
-                        "subscribers_count": {
-                          "type": "integer"
-                        },
-                        "network_count": {
-                          "type": "integer"
-                        },
-                        "code_of_conduct": {
-                          "title": "Code Of Conduct",
-                          "description": "Code Of Conduct",
-                          "type": "object",
-                          "properties": {
-                            "key": {
-                              "type": "string",
-                              "example": "contributor_covenant"
-                            },
-                            "name": {
-                              "type": "string",
-                              "example": "Contributor Covenant"
-                            },
-                            "url": {
-                              "type": "string",
-                              "format": "uri",
-                              "example": "https://api.github.com/codes_of_conduct/contributor_covenant"
-                            },
-                            "body": {
-                              "type": "string",
-                              "example": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.\n\n## Our Standards\n\nExamples of behavior that contributes to creating a positive environment include:\n\n* Using welcoming and inclusive language\n* Being respectful of differing viewpoints and experiences\n* Gracefully accepting constructive criticism\n* Focusing on what is best for the community\n* Showing empathy towards other community members\n\nExamples of unacceptable behavior by participants include:\n\n* The use of sexualized language or imagery and unwelcome sexual attention or advances\n* Trolling, insulting/derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or electronic address, without explicit permission\n* Other conduct which could reasonably be considered inappropriate in a professional setting\n\n## Our Responsibilities\n\nProject maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response\n                  to any instances of unacceptable behavior.\n\nProject maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.\n\n## Scope\n\nThis Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address,\n                  posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [EMAIL]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.\n\nProject maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]\n\n[homepage]: http://contributor-covenant.org\n[version]: http://contributor-covenant.org/version/1/4/\n"
-                            },
-                            "html_url": {
-                              "type": "string",
-                              "format": "uri",
-                              "nullable": true
-                            }
-                          },
-                          "required": [
-                            "url",
-                            "html_url",
-                            "key",
-                            "name"
-                          ]
-                        },
-                        "license": {
-                          "type": "object",
-                          "properties": {
-                            "key": {
-                              "type": "string"
-                            },
-                            "name": {
-                              "type": "string"
-                            },
-                            "spdx_id": {
-                              "type": "string"
-                            },
-                            "url": {
-                              "type": "string"
-                            },
-                            "node_id": {
-                              "type": "string"
-                            }
-                          },
-                          "nullable": true
-                        },
-                        "forks": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "open_issues": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "watchers": {
-                          "type": "integer",
-                          "example": 0
-                        },
-                        "allow_forking": {
-                          "type": "boolean"
-                        }
-                      },
-                      "required": [
-                        "archive_url",
-                        "assignees_url",
-                        "blobs_url",
-                        "branches_url",
-                        "collaborators_url",
-                        "comments_url",
-                        "commits_url",
-                        "compare_url",
-                        "contents_url",
-                        "contributors_url",
-                        "deployments_url",
-                        "description",
-                        "downloads_url",
-                        "events_url",
-                        "fork",
-                        "forks_url",
-                        "full_name",
-                        "git_commits_url",
-                        "git_refs_url",
-                        "git_tags_url",
-                        "hooks_url",
-                        "html_url",
-                        "id",
-                        "node_id",
-                        "issue_comment_url",
-                        "issue_events_url",
-                        "issues_url",
-                        "keys_url",
-                        "labels_url",
-                        "languages_url",
-                        "merges_url",
-                        "milestones_url",
-                        "name",
-                        "notifications_url",
-                        "owner",
-                        "private",
-                        "pulls_url",
-                        "releases_url",
-                        "stargazers_url",
-                        "statuses_url",
-                        "subscribers_url",
-                        "subscription_url",
-                        "tags_url",
-                        "teams_url",
-                        "trees_url",
-                        "url"
-                      ]
-                    },
-                    "head_repository_id": {
-                      "type": "integer",
-                      "example": 5
-                    }
-                  },
-                  "required": [
-                    "id",
-                    "node_id",
-                    "head_branch",
-                    "run_number",
-                    "event",
-                    "status",
-                    "conclusion",
-                    "head_sha",
-                    "workflow_id",
-                    "url",
-                    "html_url",
-                    "created_at",
-                    "updated_at",
-                    "head_commit",
-                    "head_repository",
-                    "repository",
-                    "jobs_url",
-                    "logs_url",
-                    "check_suite_url",
-                    "cancel_url",
-                    "rerun_url",
-                    "artifacts_url",
-                    "workflow_url",
-                    "pull_requests"
-                  ]
-                },
-                "examples": {
-                  "default": {
-                    "value": {
-                      "id": 30433642,
-                      "name": "Build",
-                      "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==",
-                      "check_suite_id": 42,
-                      "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==",
-                      "head_branch": "master",
-                      "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d",
-                      "run_number": 562,
-                      "event": "push",
-                      "status": "queued",
-                      "conclusion": null,
-                      "workflow_id": 159038,
-                      "url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642",
-                      "html_url": "https://github.com/octo-org/octo-repo/actions/runs/30433642",
-                      "pull_requests": [
-
-                      ],
-                      "created_at": "2020-01-22T19:33:08Z",
-                      "updated_at": "2020-01-22T19:33:08Z",
-                      "jobs_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/jobs",
-                      "logs_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/logs",
-                      "check_suite_url": "https://api.github.com/repos/octo-org/octo-repo/check-suites/414944374",
-                      "artifacts_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/artifacts",
-                      "cancel_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/cancel",
-                      "rerun_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/rerun",
-                      "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038",
-                      "head_commit": {
-                        "id": "acb5820ced9479c074f688cc328bf03f341a511d",
-                        "tree_id": "d23f6eedb1e1b9610bbc754ddb5197bfe7271223",
-                        "message": "Create linter.yaml",
-                        "timestamp": "2020-01-22T19:33:05Z",
-                        "author": {
-                          "name": "Octo Cat",
-                          "email": "octocat@github.com"
-                        },
-                        "committer": {
-                          "name": "GitHub",
-                          "email": "noreply@github.com"
-                        }
-                      },
-                      "repository": {
-                        "id": 1296269,
-                        "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
-                        "name": "Hello-World",
-                        "full_name": "octocat/Hello-World",
-                        "owner": {
-                          "login": "octocat",
-                          "id": 1,
-                          "node_id": "MDQ6VXNlcjE=",
-                          "avatar_url": "https://github.com/images/error/octocat_happy.gif",
-                          "gravatar_id": "",
-                          "url": "https://api.github.com/users/octocat",
-                          "html_url": "https://github.com/octocat",
-                          "followers_url": "https://api.github.com/users/octocat/followers",
-                          "following_url": "https://api.github.com/users/octocat/following{/other_user}",
-                          "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
-                          "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
-                          "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
-                          "organizations_url": "https://api.github.com/users/octocat/orgs",
-                          "repos_url": "https://api.github.com/users/octocat/repos",
-                          "events_url": "https://api.github.com/users/octocat/events{/privacy}",
-                          "received_events_url": "https://api.github.com/users/octocat/received_events",
-                          "type": "User",
-                          "site_admin": false
-                        },
-                        "private": false,
-                        "html_url": "https://github.com/octocat/Hello-World",
-                        "description": "This your first repo!",
-                        "fork": false,
-                        "url": "https://api.github.com/repos/octocat/Hello-World",
-                        "archive_url": "https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}",
-                        "assignees_url": "https://api.github.com/repos/octocat/Hello-World/assignees{/user}",
-                        "blobs_url": "https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}",
-                        "branches_url": "https://api.github.com/repos/octocat/Hello-World/branches{/branch}",
-                        "collaborators_url": "https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}",
-                        "comments_url": "https://api.github.com/repos/octocat/Hello-World/comments{/number}",
-                        "commits_url": "https://api.github.com/repos/octocat/Hello-World/commits{/sha}",
-                        "compare_url": "https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}",
-                        "contents_url": "https://api.github.com/repos/octocat/Hello-World/contents/{+path}",
-                        "contributors_url": "https://api.github.com/repos/octocat/Hello-World/contributors",
-                        "deployments_url": "https://api.github.com/repos/octocat/Hello-World/deployments",
-                        "downloads_url": "https://api.github.com/repos/octocat/Hello-World/downloads",
-                        "events_url": "https://api.github.com/repos/octocat/Hello-World/events",
-                        "forks_url": "https://api.github.com/repos/octocat/Hello-World/forks",
-                        "git_commits_url": "https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}",
-                        "git_refs_url": "https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}",
-                        "git_tags_url": "https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}",
-                        "git_url": "git:github.com/octocat/Hello-World.git",
-                        "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}",
-                        "issue_events_url": "https://api.github.com/repos/octocat/Hello-World/issues/events{/number}",
-                        "issues_url": "https://api.github.com/repos/octocat/Hello-World/issues{/number}",
-                        "keys_url": "https://api.github.com/repos/octocat/Hello-World/keys{/key_id}",
-                        "labels_url": "https://api.github.com/repos/octocat/Hello-World/labels{/name}",
-                        "languages_url": "https://api.github.com/repos/octocat/Hello-World/languages",
-                        "merges_url": "https://api.github.com/repos/octocat/Hello-World/merges",
-                        "milestones_url": "https://api.github.com/repos/octocat/Hello-World/milestones{/number}",
-                        "notifications_url": "https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}",
-                        "pulls_url": "https://api.github.com/repos/octocat/Hello-World/pulls{/number}",
-                        "releases_url": "https://api.github.com/repos/octocat/Hello-World/releases{/id}",
-                        "ssh_url": "git@github.com:octocat/Hello-World.git",
-                        "stargazers_url": "https://api.github.com/repos/octocat/Hello-World/stargazers",
-                        "statuses_url": "https://api.github.com/repos/octocat/Hello-World/statuses/{sha}",
-                        "subscribers_url": "https://api.github.com/repos/octocat/Hello-World/subscribers",
-                        "subscription_url": "https://api.github.com/repos/octocat/Hello-World/subscription",
-                        "tags_url": "https://api.github.com/repos/octocat/Hello-World/tags",
-                        "teams_url": "https://api.github.com/repos/octocat/Hello-World/teams",
-                        "trees_url": "https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}",
-                        "hooks_url": "http://api.github.com/repos/octocat/Hello-World/hooks"
-                      },
-                      "head_repository": {
-                        "id": 217723378,
-                        "node_id": "MDEwOlJlcG9zaXRvcnkyMTc3MjMzNzg=",
-                        "name": "octo-repo",
-                        "full_name": "octo-org/octo-repo",
-                        "private": true,
-                        "owner": {
-                          "login": "octocat",
-                          "id": 1,
-                          "node_id": "MDQ6VXNlcjE=",
-                          "avatar_url": "https://github.com/images/error/octocat_happy.gif",
-                          "gravatar_id": "",
-                          "url": "https://api.github.com/users/octocat",
-                          "html_url": "https://github.com/octocat",
-                          "followers_url": "https://api.github.com/users/octocat/followers",
-                          "following_url": "https://api.github.com/users/octocat/following{/other_user}",
-                          "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
-                          "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
-                          "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
-                          "organizations_url": "https://api.github.com/users/octocat/orgs",
-                          "repos_url": "https://api.github.com/users/octocat/repos",
-                          "events_url": "https://api.github.com/users/octocat/events{/privacy}",
-                          "received_events_url": "https://api.github.com/users/octocat/received_events",
-                          "type": "User",
-                          "site_admin": false
-                        },
-                        "html_url": "https://github.com/octo-org/octo-repo",
-                        "description": null,
-                        "fork": false,
-                        "url": "https://api.github.com/repos/octo-org/octo-repo",
-                        "forks_url": "https://api.github.com/repos/octo-org/octo-repo/forks",
-                        "keys_url": "https://api.github.com/repos/octo-org/octo-repo/keys{/key_id}",
-                        "collaborators_url": "https://api.github.com/repos/octo-org/octo-repo/collaborators{/collaborator}",
-                        "teams_url": "https://api.github.com/repos/octo-org/octo-repo/teams",
-                        "hooks_url": "https://api.github.com/repos/octo-org/octo-repo/hooks",
-                        "issue_events_url": "https://api.github.com/repos/octo-org/octo-repo/issues/events{/number}",
-                        "events_url": "https://api.github.com/repos/octo-org/octo-repo/events",
-                        "assignees_url": "https://api.github.com/repos/octo-org/octo-repo/assignees{/user}",
-                        "branches_url": "https://api.github.com/repos/octo-org/octo-repo/branches{/branch}",
-                        "tags_url": "https://api.github.com/repos/octo-org/octo-repo/tags",
-                        "blobs_url": "https://api.github.com/repos/octo-org/octo-repo/git/blobs{/sha}",
-                        "git_tags_url": "https://api.github.com/repos/octo-org/octo-repo/git/tags{/sha}",
-                        "git_refs_url": "https://api.github.com/repos/octo-org/octo-repo/git/refs{/sha}",
-                        "trees_url": "https://api.github.com/repos/octo-org/octo-repo/git/trees{/sha}",
-                        "statuses_url": "https://api.github.com/repos/octo-org/octo-repo/statuses/{sha}",
-                        "languages_url": "https://api.github.com/repos/octo-org/octo-repo/languages",
-                        "stargazers_url": "https://api.github.com/repos/octo-org/octo-repo/stargazers",
-                        "contributors_url": "https://api.github.com/repos/octo-org/octo-repo/contributors",
-                        "subscribers_url": "https://api.github.com/repos/octo-org/octo-repo/subscribers",
-                        "subscription_url": "https://api.github.com/repos/octo-org/octo-repo/subscription",
-                        "commits_url": "https://api.github.com/repos/octo-org/octo-repo/commits{/sha}",
-                        "git_commits_url": "https://api.github.com/repos/octo-org/octo-repo/git/commits{/sha}",
-                        "comments_url": "https://api.github.com/repos/octo-org/octo-repo/comments{/number}",
-                        "issue_comment_url": "https://api.github.com/repos/octo-org/octo-repo/issues/comments{/number}",
-                        "contents_url": "https://api.github.com/repos/octo-org/octo-repo/contents/{+path}",
-                        "compare_url": "https://api.github.com/repos/octo-org/octo-repo/compare/{base}...{head}",
-                        "merges_url": "https://api.github.com/repos/octo-org/octo-repo/merges",
-                        "archive_url": "https://api.github.com/repos/octo-org/octo-repo/{archive_format}{/ref}",
-                        "downloads_url": "https://api.github.com/repos/octo-org/octo-repo/downloads",
-                        "issues_url": "https://api.github.com/repos/octo-org/octo-repo/issues{/number}",
-                        "pulls_url": "https://api.github.com/repos/octo-org/octo-repo/pulls{/number}",
-                        "milestones_url": "https://api.github.com/repos/octo-org/octo-repo/milestones{/number}",
-                        "notifications_url": "https://api.github.com/repos/octo-org/octo-repo/notifications{?since,all,participating}",
-                        "labels_url": "https://api.github.com/repos/octo-org/octo-repo/labels{/name}",
-                        "releases_url": "https://api.github.com/repos/octo-org/octo-repo/releases{/id}",
-                        "deployments_url": "https://api.github.com/repos/octo-org/octo-repo/deployments"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        "x-github": {
-          "githubCloudOnly": false,
-          "enabledForGitHubApps": true,
-          "category": "actions",
-          "subcategory": "workflow-runs"
-        }
-      }
-    },
-    "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs": {
-      "get": {
-        "summary": "List jobs for a workflow run attempt",
-        "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#parameters).",
-        "tags": [
-          "actions"
-        ],
-        "operationId": "actions/list-jobs-for-workflow-run-attempt",
-        "externalDocs": {
-          "description": "API method documentation",
-          "url": "https://docs.github.com/enterprise-server@3.3/rest/reference/actions#list-jobs-for-a-workflow-run-attempt"
-        },
-        "parameters": [
-          {
-            "name": "owner",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "repo",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "string"
-            }
-          },
-          {
-            "name": "run_id",
-            "description": "The id of the workflow run.",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          },
-          {
-            "name": "attempt_number",
-            "description": "The attempt number of the workflow run.",
-            "in": "path",
-            "required": true,
-            "schema": {
-              "type": "integer"
-            }
-          },
-          {
-            "name": "per_page",
-            "description": "Results per page (max 100)",
-            "in": "query",
-            "schema": {
-              "type": "integer",
-              "default": 30
-            }
-          },
-          {
-            "name": "page",
-            "description": "Page number of the results to fetch.",
-            "in": "query",
-            "schema": {
-              "type": "integer",
-              "default": 1
-            }
-          }
-        ],
-        "responses": {
-          "200": {
-            "description": "Response",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "type": "object",
-                  "required": [
-                    "total_count",
-                    "jobs"
-                  ],
-                  "properties": {
-                    "total_count": {
-                      "type": "integer"
-                    },
-                    "jobs": {
-                      "type": "array",
-                      "items": {
-                        "title": "Job",
-                        "description": "Information of a job execution in a workflow run",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "description": "The id of the job.",
-                            "example": 21,
-                            "type": "integer"
-                          },
-                          "run_id": {
-                            "description": "The id of the associated workflow run.",
-                            "example": 5,
-                            "type": "integer"
-                          },
-                          "run_url": {
-                            "type": "string",
-                            "example": "https://api.github.com/repos/github/hello-world/actions/runs/5"
-                          },
-                          "run_attempt": {
-                            "type": "integer",
-                            "description": "Attempt number of the associated workflow run, 1 for first attempt and higher if the workflow was re-run.",
-                            "example": 1
-                          },
-                          "node_id": {
-                            "type": "string",
-                            "example": "MDg6Q2hlY2tSdW40"
-                          },
-                          "head_sha": {
-                            "description": "The SHA of the commit that is being run.",
-                            "example": "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d",
-                            "type": "string"
-                          },
-                          "url": {
-                            "type": "string",
-                            "example": "https://api.github.com/repos/github/hello-world/actions/jobs/21"
-                          },
-                          "html_url": {
-                            "type": "string",
-                            "example": "https://github.com/github/hello-world/runs/4",
-                            "nullable": true
-                          },
-                          "status": {
-                            "description": "The phase of the lifecycle that the job is currently in.",
-                            "example": "queued",
-                            "type": "string",
-                            "enum": [
-                              "queued",
-                              "in_progress",
-                              "completed"
-                            ]
-                          },
-                          "conclusion": {
-                            "description": "The outcome of the job.",
-                            "example": "success",
-                            "type": "string",
-                            "nullable": true
-                          },
-                          "started_at": {
-                            "description": "The time that the job started, in ISO 8601 format.",
-                            "example": "2019-08-08T08:00:00-07:00",
-                            "format": "date-time",
-                            "type": "string"
-                          },
-                          "completed_at": {
-                            "description": "The time that the job finished, in ISO 8601 format.",
-                            "example": "2019-08-08T08:00:00-07:00",
-                            "format": "date-time",
-                            "type": "string",
-                            "nullable": true
-                          },
-                          "name": {
-                            "description": "The name of the job.",
-                            "example": "test-coverage",
-                            "type": "string"
-                          },
-                          "steps": {
-                            "description": "Steps in this job.",
-                            "type": "array",
-                            "items": {
-                              "type": "object",
-                              "required": [
-                                "name",
-                                "status",
-                                "conclusion",
-                                "number"
-                              ],
-                              "properties": {
-                                "status": {
-                                  "description": "The phase of the lifecycle that the job is currently in.",
-                                  "example": "queued",
-                                  "type": "string",
-                                  "enum": [
-                                    "queued",
-                                    "in_progress",
-                                    "completed"
-                                  ]
-                                },
-                                "conclusion": {
-                                  "description": "The outcome of the job.",
-                                  "example": "success",
-                                  "type": "string",
-                                  "nullable": true
-                                },
-                                "name": {
-                                  "description": "The name of the job.",
-                                  "example": "test-coverage",
-                                  "type": "string"
-                                },
-                                "number": {
-                                  "type": "integer",
-                                  "example": 1
-                                },
-                                "started_at": {
-                                  "description": "The time that the step started, in ISO 8601 format.",
-                                  "example": "2019-08-08T08:00:00-07:00",
-                                  "format": "date-time",
-                                  "type": "string",
-                                  "nullable": true
-                                },
-                                "completed_at": {
-                                  "description": "The time that the job finished, in ISO 8601 format.",
-                                  "example": "2019-08-08T08:00:00-07:00",
-                                  "format": "date-time",
-                                  "type": "string",
-                                  "nullable": true
-                                }
-                              }
-                            }
-                          },
-                          "check_run_url": {
-                            "type": "string",
-                            "example": "https://api.github.com/repos/github/hello-world/check-runs/4"
-                          },
-                          "labels": {
-                            "type": "array",
-                            "items": {
-                              "type": "string"
-                            },
-                            "description": "Labels for the workflow job. Specified by the \"runs_on\" attribute in the action's workflow file.",
-                            "example": [
-                              "self-hosted",
-                              "foo",
-                              "bar"
-                            ]
-                          },
-                          "runner_id": {
-                            "type": "integer",
-                            "nullable": true,
-                            "example": 1,
-                            "description": "The ID of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)"
-                          },
-                          "runner_name": {
-                            "type": "string",
-                            "nullable": true,
-                            "example": "my runner",
-                            "description": "The name of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)"
-                          },
-                          "runner_group_id": {
-                            "type": "integer",
-                            "nullable": true,
-                            "example": 2,
-                            "description": "The ID of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)"
-                          },
-                          "runner_group_name": {
-                            "type": "string",
-                            "nullable": true,
-                            "example": "my runner group",
-                            "description": "The name of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)"
-                          }
-                        },
-                        "required": [
-                          "id",
-                          "node_id",
-                          "run_id",
-                          "run_url",
-                          "head_sha",
-                          "name",
-                          "url",
-                          "html_url",
-                          "status",
-                          "conclusion",
-                          "started_at",
-                          "completed_at",
-                          "check_run_url",
-                          "labels",
-                          "runner_id",
-                          "runner_name",
-                          "runner_group_id",
-                          "runner_group_name"
-                        ]
-                      }
-                    }
-                  }
-                },
-                "examples": {
-                  "default": {
-                    "value": {
-                      "total_count": 1,
-                      "jobs": [
-                        {
-                          "id": 399444496,
-                          "run_id": 29679449,
-                          "run_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449",
-                          "node_id": "MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==",
-                          "head_sha": "f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0",
-                          "url": "https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496",
-                          "html_url": "https://github.com/octo-org/octo-repo/runs/399444496",
-                          "status": "completed",
-                          "conclusion": "success",
-                          "started_at": "2020-01-20T17:42:40Z",
-                          "completed_at": "2020-01-20T17:44:39Z",
-                          "name": "build",
-                          "steps": [
-                            {
-                              "name": "Set up job",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 1,
-                              "started_at": "2020-01-20T09:42:40.000-08:00",
-                              "completed_at": "2020-01-20T09:42:41.000-08:00"
-                            },
-                            {
-                              "name": "Run actions/checkout@v2",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 2,
-                              "started_at": "2020-01-20T09:42:41.000-08:00",
-                              "completed_at": "2020-01-20T09:42:45.000-08:00"
-                            },
-                            {
-                              "name": "Set up Ruby",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 3,
-                              "started_at": "2020-01-20T09:42:45.000-08:00",
-                              "completed_at": "2020-01-20T09:42:45.000-08:00"
-                            },
-                            {
-                              "name": "Run actions/cache@v2",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 4,
-                              "started_at": "2020-01-20T09:42:45.000-08:00",
-                              "completed_at": "2020-01-20T09:42:48.000-08:00"
-                            },
-                            {
-                              "name": "Install Bundler",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 5,
-                              "started_at": "2020-01-20T09:42:48.000-08:00",
-                              "completed_at": "2020-01-20T09:42:52.000-08:00"
-                            },
-                            {
-                              "name": "Install Gems",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 6,
-                              "started_at": "2020-01-20T09:42:52.000-08:00",
-                              "completed_at": "2020-01-20T09:42:53.000-08:00"
-                            },
-                            {
-                              "name": "Run Tests",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 7,
-                              "started_at": "2020-01-20T09:42:53.000-08:00",
-                              "completed_at": "2020-01-20T09:42:59.000-08:00"
-                            },
-                            {
-                              "name": "Deploy to Heroku",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 8,
-                              "started_at": "2020-01-20T09:42:59.000-08:00",
-                              "completed_at": "2020-01-20T09:44:39.000-08:00"
-                            },
-                            {
-                              "name": "Post actions/cache@v2",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 16,
-                              "started_at": "2020-01-20T09:44:39.000-08:00",
-                              "completed_at": "2020-01-20T09:44:39.000-08:00"
-                            },
-                            {
-                              "name": "Complete job",
-                              "status": "completed",
-                              "conclusion": "success",
-                              "number": 17,
-                              "started_at": "2020-01-20T09:44:39.000-08:00",
-                              "completed_at": "2020-01-20T09:44:39.000-08:00"
-                            }
-                          ],
-                          "check_run_url": "https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496",
-                          "labels": [
-                            "self-hosted",
-                            "foo",
-                            "bar"
-                          ],
-                          "runner_id": 1,
-                          "runner_name": "my runner",
-                          "runner_group_id": 2,
-                          "runner_group_name": "my runner group"
-                        }
-                      ]
-                    }
-                  }
-                }
-              }
-            },
-            "headers": {
-              "Link": {
-                "example": "<https://api.github.com/resource?page=2>; rel=\"next\", <https://api.github.com/resource?page=5>; rel=\"last\"",
-                "schema": {
-                  "type": "string"
-                }
-              }
-            }
-          },
-          "404": {
-            "description": "Resource not found",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "title": "Basic Error",
-                  "description": "Basic Error",
-                  "type": "object",
-                  "properties": {
-                    "message": {
-                      "type": "string"
-                    },
-                    "documentation_url": {
-                      "type": "string"
-                    },
-                    "url": {
-                      "type": "string"
-                    },
-                    "status": {
-                      "type": "string"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        "x-github": {
-          "githubCloudOnly": false,
-          "enabledForGitHubApps": true,
-          "category": "actions",
-          "subcategory": "workflow-jobs"
-        }
-      }
-    },
     "/repos/{owner}/{repo}/actions/runs/{run_id}/cancel": {
       "post": {
         "summary": "Cancel a workflow run",
@@ -134675,6 +130328,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/enterprise-server@3.3/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -256590,7 +252244,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -256891,7 +252545,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/enterprise-server@3.3/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index 78cdfe6800..b9a72632a6 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -59223,11 +59223,10 @@
                   },
                   "permission": {
                     "type": "string",
-                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.  \n\\* `admin` - team members can pull, push and administer newly-added repositories.",
+                    "description": "**Deprecated**. The permission that new repositories will be added to the team with when none is specified. Can be one of:  \n\\* `pull` - team members can pull, but not push to or administer newly-added repositories.  \n\\* `push` - team members can pull and push, but not administer newly-added repositories.",
                     "enum": [
                       "pull",
-                      "push",
-                      "admin"
+                      "push"
                     ],
                     "default": "pull"
                   },
@@ -59243,7 +59242,7 @@
               "example": {
                 "name": "Justice League",
                 "description": "A great team",
-                "permission": "admin",
+                "permission": "push",
                 "privacy": "closed"
               }
             }
@@ -88791,6 +88790,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -103315,6 +103315,7 @@
           },
           {
             "name": "created",
+            "description": "Returns workflow runs created within the given date-time range. For more information on the syntax, see \"[Understanding the search syntax](https://docs.github.com/github-ae@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).\"",
             "in": "query",
             "required": false,
             "schema": {
@@ -223356,7 +223357,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to add to the issue's existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also replace all of the labels for an issue. For more information, see \"[Set labels for an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#set-labels-for-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
@@ -223657,7 +223658,7 @@
                       "labels": {
                         "type": "array",
                         "minItems": 1,
-                        "description": "The names of the labels to add to the issue. You can pass an empty array to remove all labels. **Note:** Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key.",
+                        "description": "The names of the labels to set for the issue. The labels you set replace any existing labels. You can pass an empty array to remove all labels. Alternatively, you can pass a single label as a `string` or an `array` of labels directly, but GitHub recommends passing an object with the `labels` key. You can also add labels to the existing labels for an issue. For more information, see \"[Add labels to an issue](https://docs.github.com/github-ae@latest/rest/reference/issues#add-labels-to-an-issue).\"",
                         "items": {
                           "type": "string"
                         }
diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br
index 97b361fbeb..9a797cb1f2 100644
--- a/lib/search/indexes/github-docs-3.0-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b353ecb8bfbd734b56c14f11cef9e15608c7e76f96ce1e7dd308ccfe771c366a
-size 648160
+oid sha256:e043d2de01f8cbaf85cd4875d1daaa7eeb69af1f5d065ff3e528263f3a77df97
+size 654500
diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br
index 3d2d3631b0..181fe60b0e 100644
--- a/lib/search/indexes/github-docs-3.0-cn.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:fe7540103fc9d3c4ab6d9f9adcaa014d2477c6cdcc8d114b6bcd0655ded61493
-size 1350089
+oid sha256:22a36605b3b94e16e0cc3eae30f4e56164db0a146318441d482f7033375b01ce
+size 1358397
diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br
index b7e3933713..8fefffe4c4 100644
--- a/lib/search/indexes/github-docs-3.0-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:af870630000442cb4790595c7ae67b7ad9cdbd1b27c855e25003b6213740f418
-size 971327
+oid sha256:35e52e83b2ff9f6255c192373b2834e5cbbc47832526ebdd6528d16aa62a47e3
+size 981510
diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br
index 9fd64ca05f..93f6525f93 100644
--- a/lib/search/indexes/github-docs-3.0-en.json.br
+++ b/lib/search/indexes/github-docs-3.0-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:23a839078e7d98b854d04ea9e2b85e871a6c28e80b7c6666b24f7a8c615153af
-size 3969006
+oid sha256:dcdb85427dfa7b81d3292371e06f85238c1d6fc1107726380fb7296a93ca121f
+size 3987849
diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br
index 73e9961226..7b63de3223 100644
--- a/lib/search/indexes/github-docs-3.0-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:26ec61e506b24590a89ee6cb0126d1993438655f41fa3543933c2bddc1c0fbd3
-size 604741
+oid sha256:b4e90ee51fa30c07862b02e2bee076ce3929f80bde660e1759cc435faf66818b
+size 615457
diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br
index fa3fab6dde..aacde69e35 100644
--- a/lib/search/indexes/github-docs-3.0-es.json.br
+++ b/lib/search/indexes/github-docs-3.0-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7f46e0c93a57dd0265beda0306038ed67406f74052bce9ea6d2cf26e7ea22554
-size 2533049
+oid sha256:1f7ca8420920a0a277aa7ec6e9542387e0003329dae174475795592aa59dae77
+size 2573818
diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br
index 9efcba1a2b..2006d83a74 100644
--- a/lib/search/indexes/github-docs-3.0-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dd641f6908aea3244890ffbbe268e0a685f23abf0ba2925f30b80a833fc23969
-size 666535
+oid sha256:754691231d729ea4ca1029ad9cb15e0621da7af196b7e8698d2fb63bfafe1eb1
+size 674596
diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br
index 3e14f5d586..a3dc129b02 100644
--- a/lib/search/indexes/github-docs-3.0-ja.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c90c7613c2b6a5f16038d33cb03dad5e6f37e412b4ad701980cd621c974a4138
-size 3533709
+oid sha256:e1827fe284936e9e0eeee3d13ba692899949d8633a1019b8ebe0d11616728722
+size 3555600
diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br
index 78bc980714..7ccc52c328 100644
--- a/lib/search/indexes/github-docs-3.0-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b45e1be94ddd7fb324be47e2c7b217505b5b49d19cbc5a01c7a647eca169a7d7
-size 595190
+oid sha256:90971a65f48a252017da39c793393f99c307427478179ebcc263ae1acad0ba47
+size 605206
diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br
index 8a5aad5b3c..34ce397ca2 100644
--- a/lib/search/indexes/github-docs-3.0-pt.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:72744fa23601da9a27944a369a0ae5ff4925a77ebadd185c1b3f952775f47229
-size 2425856
+oid sha256:41cc0b5478ce86ca451bb5882701dc0a6e9fbb5e204bc33062f4f370538954cd
+size 2469446
diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br
index df8cc4e414..bd1019dae5 100644
--- a/lib/search/indexes/github-docs-3.1-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:cba670fa561aabdbc1b82c7765c1b660fb98b9d24778527908e70b39ea844628
-size 662249
+oid sha256:b4b9746fa14d4a454dbcd684ef780c5d3bbb08c2d42d671b997dbe98b96cc351
+size 667833
diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br
index 51a3dd894c..795e4661cd 100644
--- a/lib/search/indexes/github-docs-3.1-cn.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0a8b4e7cce4a1ebb29fe789981e5813a80541927772a8110c9a19e0544d16d1d
-size 1387791
+oid sha256:3269bb665a7f5d5cd7b22297077b4077a29691295fc655412b50e56fd02381de
+size 1394511
diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br
index 87e9cedc29..74209d60cc 100644
--- a/lib/search/indexes/github-docs-3.1-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3305b077744623cc099c6de99f1438fbb9c85734a38b063f527c6318ec242083
-size 996376
+oid sha256:42a291044aefd9d56975ca3917bc65e64efb6b7e3477ae9495bf7fa589de43da
+size 1006168
diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br
index de5498fe35..cd3a4cc0f7 100644
--- a/lib/search/indexes/github-docs-3.1-en.json.br
+++ b/lib/search/indexes/github-docs-3.1-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d3758a0d0dcd9646562a5008e17b4862a8a6fa0bb0d3569d74a20910592a3325
-size 4063483
+oid sha256:25abbf58246dceeee05ea48049a8d3b30dcdd44266b4fafc4616952ec3148f8b
+size 4079287
diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br
index 251b7695f4..a280ccdee8 100644
--- a/lib/search/indexes/github-docs-3.1-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:689d5df0cd2f5496dc0c53813788d1016c8ce2f84ce14b06d00f758944256699
-size 616955
+oid sha256:ea5e2f8d7e9ab35399a62a4fdd2040be5371ce2461c3fd913264e030b7b6ad85
+size 626818
diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br
index 95657a2764..5851fb8d4b 100644
--- a/lib/search/indexes/github-docs-3.1-es.json.br
+++ b/lib/search/indexes/github-docs-3.1-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2c73fb9d25717b727df6d8acd812389ee52798517e56eb2cff514f2a439fff8f
-size 2592376
+oid sha256:99d4c44764ec050890aaf7a8ab60198e2834f0d489815827a9af721ceff254d2
+size 2633490
diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br
index 0e18be23f5..85ad352cda 100644
--- a/lib/search/indexes/github-docs-3.1-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:293d693c5f70ce224b7c3e40c05eb602d4ad1dfa4c7e46efbcf75ccd7c8bf0fd
-size 680505
+oid sha256:1bb341570d90b1073dfb1b2e70bbe8defb3195bd53e86a4a8c241e89eb398874
+size 688198
diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br
index 6fb4e85e56..3645d4e8ec 100644
--- a/lib/search/indexes/github-docs-3.1-ja.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:24ca98c6de4c9d4716763148b6910611348b71013ebd4ec58a9bf25adf567eeb
-size 3614316
+oid sha256:5f06b5ae2995795b9737732e9a076cb5ea190a4a7d5eaefd31560ed4e20a53f3
+size 3633513
diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br
index 9860b988b0..feebfa0a3b 100644
--- a/lib/search/indexes/github-docs-3.1-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:78598b3a67f26d871757293b389a64529c0688ee05db646021493c18876446b6
-size 607482
+oid sha256:621c830760ced127ffcd8d229804623fd99462539fd1f365f7b8fd4f1d471c18
+size 617462
diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br
index 53b18c4191..89e68c5e34 100644
--- a/lib/search/indexes/github-docs-3.1-pt.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be438a113263f2f291cda21ae2b016ef839741dce5ccbf8df3e507727fc61f12
-size 2479424
+oid sha256:0aa3287747e093e84ac731467d96a1012f265b24a6b0137ee2cf1efd4f7eef66
+size 2519970
diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br
index 65f7d18b18..4bceb2b8a3 100644
--- a/lib/search/indexes/github-docs-3.2-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a347e461a03c909df5a986131ca9eed4dd5abce9ad7d805c843f721246ca991c
-size 677193
+oid sha256:9c31b1748512bc639933cb014ef4b76cc5c8b287021ee7ad1705e9d3857f6d66
+size 684155
diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br
index 99d984d564..09bca1f48f 100644
--- a/lib/search/indexes/github-docs-3.2-cn.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b7d5f541bb47c2364643e57acbad86f43feae7f2aadc3f96837247b5c76a874c
-size 1418375
+oid sha256:f19b3303626c8c8f603571fe4f52f12f9556c9e7d096d40f12828089f5c4a69b
+size 1426591
diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br
index 6fde575e0d..05de556984 100644
--- a/lib/search/indexes/github-docs-3.2-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:73191f6ddaebae0a5c9adc10828e0e22d283771a442ac173f990394acadf6546
-size 1032671
+oid sha256:2829deefc251cbea348e6e2bd0cf1b0bd43a8cf15d850592176c4bbbb69011ef
+size 1038423
diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br
index 9b88019d92..7e38abee47 100644
--- a/lib/search/indexes/github-docs-3.2-en.json.br
+++ b/lib/search/indexes/github-docs-3.2-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:37499ad6b11b8a9489c81276b30c9133aa2d814404c3ab458093f8214cb8a456
-size 4193896
+oid sha256:3fc064fd4e4c5cce31bd8024d2d8c9e0a750397551f920738d10e2b5ad4052ee
+size 4213925
diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br
index 36e46f0d58..bbfbbf696c 100644
--- a/lib/search/indexes/github-docs-3.2-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:db62be5a7e205031de7299359155a53e6167551550366b59d7d4a09e826aaa4f
-size 631074
+oid sha256:a46908a7c0da6629d96e21463117ae29d71b5e158b182f6598a6459b6c7c41e3
+size 641557
diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br
index d5a94c4ab2..5fdb0b6bc4 100644
--- a/lib/search/indexes/github-docs-3.2-es.json.br
+++ b/lib/search/indexes/github-docs-3.2-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:51ae3d2ac54da9a3d4e3c0312a507a5f3654ec2126ac0bf812213685b45d8a68
-size 2652341
+oid sha256:75b0607cabfa90444ca8663e9ddac71d9cd6e66181b1d9c8ce74605bd8b4ef56
+size 2696999
diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br
index c7e26312cc..fc72c7c6a9 100644
--- a/lib/search/indexes/github-docs-3.2-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0137abfd59e069bd057941ff6aa0e326b9b720bc40a6cfbc6b2207e3697c0d35
-size 694193
+oid sha256:acf7d09a4d1b53c53b98c127c7e767922f53200556a7a96d992c982e619c4381
+size 700579
diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br
index db65cc8d3b..4fbafd7c88 100644
--- a/lib/search/indexes/github-docs-3.2-ja.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:244f3d15a40cd2212850312625e73d761648cfaba412b2f50e9757d2ea98cf09
-size 3691970
+oid sha256:d9422294539a9cb22995b6f0ff0e1428fdee4ed29173278ef7c8da6235f7f289
+size 3709590
diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br
index c7acf54891..5998908719 100644
--- a/lib/search/indexes/github-docs-3.2-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:56fa9b77de31d80afc3d4031b3c3517d533038f638811759f311a1a0dcd9a33e
-size 620767
+oid sha256:7751bdfe77e6972dfbda6257f4401699d439506763df66f1cbf94988f9783b78
+size 632113
diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br
index 37de0f10b4..500a34ad18 100644
--- a/lib/search/indexes/github-docs-3.2-pt.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3ef64ff7088b25c5cce32394e6b8136221384d5c4ba974aeebeb3846d5c32c01
-size 2533143
+oid sha256:3d22f82ae074a4ea68a0ef89dede7d5f2eb6313c545a74fdc968a821f22178c3
+size 2581272
diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br
index e73ae92459..1f8fdafc8f 100644
--- a/lib/search/indexes/github-docs-3.3-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5e60e9fb991ea335e76fadf7ba4aa94841c145b8bdd61c244e1030c26e391789
-size 699195
+oid sha256:50b9d51de10f5c619184f9dc96176a970c63fccb4cd06358c8695198c2de713d
+size 706530
diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br
index 700f558653..bfc9cb4195 100644
--- a/lib/search/indexes/github-docs-3.3-cn.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c5d6159422d5e76d6675b43362933d2d52aa9ddae7b709612c848d55b7ef4580
-size 1477107
+oid sha256:d2e17631650865d3b5f781a808b663bd9edd97ab184843969849da97e7a4cf60
+size 1485351
diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br
index 9d587af04d..35518521a7 100644
--- a/lib/search/indexes/github-docs-3.3-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0bc94bd0b6432ecccd7ba4c035f44e2a3c351d9176312833026d2200e38c1c19
-size 1068391
+oid sha256:d684511cef46b30418448bb63017bbf76b1592a88b9294689f4ae00c052acdee
+size 1078847
diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br
index f68620ab4b..303b6f977c 100644
--- a/lib/search/indexes/github-docs-3.3-en.json.br
+++ b/lib/search/indexes/github-docs-3.3-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:692f5a389c334a590e83bae4fd1f014061a44c65f0cc84f44fcf52dc73983b3e
-size 4299297
+oid sha256:1c51e02956166c1ec757dc8f9c3d958f2206db1264687557c7f007208f515d71
+size 4317198
diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br
index 7cfc0adc55..5d934cfbab 100644
--- a/lib/search/indexes/github-docs-3.3-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c1b1c220a08c8937e02452d29eef86e1ec44ff6839bf6fa893d6a3b8f2792e67
-size 650206
+oid sha256:07dc9e22522628c606e143421f9d2abcc1a5ec17e27cf379e6576d4fe39b32fa
+size 661097
diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br
index f19838cb36..15d04128b4 100644
--- a/lib/search/indexes/github-docs-3.3-es.json.br
+++ b/lib/search/indexes/github-docs-3.3-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:63622368d28176f03060f9f5b5f00257b8717cb090c72684ed7ab766233eea0b
-size 2752028
+oid sha256:d21ac842bc650004783951ab7476675369e371cb1cf4cfc4cec4df6cf3ea9070
+size 2798003
diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br
index f6c7e732ca..3858bb0360 100644
--- a/lib/search/indexes/github-docs-3.3-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d14491d5d8b374bc508b88c7202573d05ca0d04133d2625c21fec4f824d7780c
-size 716598
+oid sha256:de1c04154efefa917f52662187816d5c05903197a081916b1dc90e2283b1c909
+size 724584
diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br
index 7fdf4eb2ef..0ab92b423d 100644
--- a/lib/search/indexes/github-docs-3.3-ja.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0ff81f27428d02d7cc37cc3630a18c0a3f6e59d363d27d803b736042fea15065
-size 3815571
+oid sha256:9269687e110469f3e4b7f6a3cd1ef6f800b8eb9073a1003f8e8e9e6a7c5fa361
+size 3838064
diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br
index fd135fb33f..63f9e3b91c 100644
--- a/lib/search/indexes/github-docs-3.3-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:45c3292fe4864601965dec3a477641d571030e8c5e596c56ff677e40532ac863
-size 639670
+oid sha256:6e83fc69ff7491601e7dc7b002e9e10c853470b973584ea462e35af68eb36d22
+size 651954
diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br
index f7676e59d4..a7f4b51de5 100644
--- a/lib/search/indexes/github-docs-3.3-pt.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ba12aa6402868cdb88b7b4aed224143bd82a3a252789a6b20407f8425a62ebf6
-size 2615070
+oid sha256:0484642b862cc0659fcb696c41ea5f2f4efe60296ee06b06e5432c81e34ec2d5
+size 2662297
diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
index 53cb46b057..750ee34502 100644
--- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3841316352920f4779cad1a2cce2fec65253527150715810379e02829e826b02
-size 891781
+oid sha256:c1513134bf409a43f84f0119cab3501981a87a9ec2404ac96364d2aea2432423
+size 900209
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index c9d7ca380f..546ed01d81 100644
--- a/lib/search/indexes/github-docs-dotcom-cn.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9c574f14c5b328e6492b8ab3f2222b92e7195b1560387b9c576424d4999ec705
-size 1627488
+oid sha256:5fc3e26004f666bd4b71ff45b2d5ed2d70640f0590ec6e27880a3ab56bf151d6
+size 1634852
diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br
index 4c0a995d4e..f39f213b23 100644
--- a/lib/search/indexes/github-docs-dotcom-en-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3928c2e01ee00f15fa7cd79bafc08209a5244f3738a742229144abc5397193d2
-size 1347980
+oid sha256:5bf3cbf7114cfea61aeda75eb15aa4667e98869ad8ec5d4f8091afea3686063e
+size 1365222
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 88299675d2..571ac0be1e 100644
--- a/lib/search/indexes/github-docs-dotcom-en.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:491907a631ced2a89da8ab6d76f731645c1d9b32e5ad24efeeefc832450deb45
-size 5159968
+oid sha256:50aa2fc1b23a00bebb4f143fc04d596f2c4007f7b54f2f61ea2aafdb26b62ecf
+size 5201905
diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br
index b061d7d8a4..fbd7e15488 100644
--- a/lib/search/indexes/github-docs-dotcom-es-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e66a51502be2c27e4a8318a3866c343bd1b282f09ee5b6d08e4c5adb0c777856
-size 812893
+oid sha256:ec45cb7d4ca4af66d7ae2381c7893a15965e73c5a2b98db0615140a46e452344
+size 830958
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 699728a482..695d64a561 100644
--- a/lib/search/indexes/github-docs-dotcom-es.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b9a5c2266ac20d3633569b1dc170be9decd998519cd04b4c02e6244be68023f0
-size 3272950
+oid sha256:b3da95473cdf8ed9081e50af9eb2506855e6f54047be3d227bd3b354db00f985
+size 3350610
diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
index f7ef69ef76..3e8673a813 100644
--- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0a034e143066e74ac0b705e027e48748c41cf1d4de2b965d5289a4eb76e0adcf
-size 908819
+oid sha256:ae27ce57bbab4e7945a3c1c1763a94ab08afa75f3d16da81059d2e169f0aa0bd
+size 919437
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index b24fa15c19..4cdbcd98bf 100644
--- a/lib/search/indexes/github-docs-dotcom-ja.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d39956fae1715294702cbedad9f4a680fb4c7b462baa00174841f83cfad06d0a
-size 4626317
+oid sha256:7d1f90fc3a91a18331b79b80cf6dc513357efc5b2cef18724181e849b83b24db
+size 4649822
diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
index f9995f3c21..139a67bae6 100644
--- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2395f9cc007c85b6caaf3a60ae18b081a9ce1481722c431f5e047c5b3505b6d2
-size 802173
+oid sha256:b71d4d7bb3598768c220bb88627d34e2258984a11ca1d6de7faffec481e47aa5
+size 819268
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index f9e662c526..e92a03b9f2 100644
--- a/lib/search/indexes/github-docs-dotcom-pt.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:16c918ed59895ed12b2ff4fdbb90e9b9ced2059028f1c1b4d4e8d03a2a1be4f5
-size 3120836
+oid sha256:3137fe9897e07e7bfa17293235ba4ae6b58730d96b53dada5f19afd986043c62
+size 3196984
diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br
index af145caf64..e298ba66fb 100644
--- a/lib/search/indexes/github-docs-ghae-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0be14d14535a83c8942bff8b7bda2d802b5a3bda24ffa9fb44ad5c5d445f190b
-size 547084
+oid sha256:eedf7dc1a59d7705a3bec60f35907156dd0c984e1ff2feb8e75621bf831c3b78
+size 551979
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index 0ddc6114b6..741160ab44 100644
--- a/lib/search/indexes/github-docs-ghae-cn.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f34e5d0c4cf282af9f7b06f827936b4d95f5e7b337d896a376059142f9e0fcb1
-size 1099595
+oid sha256:95ece6fd3641eb50e29af7b37f94a6d3accab400f7b6e227ef84320cf75fd612
+size 1106037
diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br
index 3d903c3fb8..49af6516c0 100644
--- a/lib/search/indexes/github-docs-ghae-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b537bbd419b64273b741ab01b55b5375c1ff32da122b128def04c106d3f196c4
-size 849120
+oid sha256:791a86f1489ff0b2ba07021a6b39b5cf05c78ed827d6e16e82a6334cc4cf42c1
+size 858165
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 33374bd6c4..60af654651 100644
--- a/lib/search/indexes/github-docs-ghae-en.json.br
+++ b/lib/search/indexes/github-docs-ghae-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d0f946923bff3348f70e221fce4f4f437ea64e39607327055a6d085e75ebdb26
-size 3406232
+oid sha256:0009bf318573e9e40e5a181550f99fa0273cbd019286e8050a4b4facf4e087bd
+size 3434265
diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br
index 75cf497b8b..84f1a82996 100644
--- a/lib/search/indexes/github-docs-ghae-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ba494c79f347772a3a3974dcd5515354b813393ed6c00cd8f7ddf899387aee9e
-size 510377
+oid sha256:1578d8ff941cff5586331b9bfa09347803bf64d02678660500b3905e023c0a12
+size 520121
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 7cbb3a10d4..27a471b130 100644
--- a/lib/search/indexes/github-docs-ghae-es.json.br
+++ b/lib/search/indexes/github-docs-ghae-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8db0e2279454731e3d886e1a5dabd137acec72ed23c5142ac76bf1a65569a5a1
-size 2074728
+oid sha256:e042e07c6abf4209f2ff9decdd790f58817a2b96bb086e2814514f76738d0b43
+size 2116559
diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br
index 17bb84cb3e..148431db06 100644
--- a/lib/search/indexes/github-docs-ghae-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0ce013329c8c04204f1e275d3ecc1e27878083c5bfe1e2c455fc002817e35d32
-size 559667
+oid sha256:8d2ea877e08a426787a6e4ab99e48b67c1dfcd714f7ca96a8511cd280926f42a
+size 564989
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index d2df6d15b1..091a930f94 100644
--- a/lib/search/indexes/github-docs-ghae-ja.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c9ccb9470b8454f4c46326e5e24b03c830df1ae55b4444c1dd99fd4bb44b18fa
-size 2868055
+oid sha256:820678d5d615c7a6857b3135ec05f1c3f0ac46b8d8209602bc6db546a95f0e19
+size 2880363
diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br
index 4007984ce9..63dcba24b7 100644
--- a/lib/search/indexes/github-docs-ghae-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:aacd1991e8ebe8fd30de392318246a1cd20d08c5a9fe8944aa0c49f35fce2fe3
-size 502973
+oid sha256:4aa0400388c746f7bcd1a19db09d57a41d9cd2110bcef0efefd1518f25727642
+size 512684
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index aca2eb5221..bc4d498824 100644
--- a/lib/search/indexes/github-docs-ghae-pt.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4026498b3850e8aed4527fa4af3a1aee82febda18088da06254a35715269cbb0
-size 1966242
+oid sha256:b70cb8e96055600d8b9eaef4f05b9c1565de0a1f192a088211be09ac3ac13486
+size 2009300
diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br
index a5f2c94106..2a16ea9bba 100644
--- a/lib/search/indexes/github-docs-ghec-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9fd2a73760b9e6987d8b9e8a0cdb38a5a31bc314d7cc0837c31df9762a2b6a6f
-size 816142
+oid sha256:0f4d10e2289c90e2a91e56e2013acbc00a69971feba536b1256e6a20f1ef874f
+size 822972
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 9cc8c127a0..6400518ba5 100644
--- a/lib/search/indexes/github-docs-ghec-cn.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1c542e8cc37a659773e7d691a2f6d3d58e9ed5d332c393dbdf90bf587beb1f0d
-size 1683639
+oid sha256:9caa96f3ddbb12fa25965a3b163cea719b5419a143f24e6c6cd5ccf16ad02a39
+size 1693122
diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br
index 884fd8255c..69a9cfef01 100644
--- a/lib/search/indexes/github-docs-ghec-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:50d90f2de4b8926d3f9e56a71d151f33aeea1a09e043ef9df8cfabf742860d34
-size 1223511
+oid sha256:7eea31028134076b9042940e4b8aa2d91ab0eb215b880a258ab41ab766057b58
+size 1239491
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index df97d8eeb3..0e3450c783 100644
--- a/lib/search/indexes/github-docs-ghec-en.json.br
+++ b/lib/search/indexes/github-docs-ghec-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2896869212b0c4edcb8e5103b90385e5afc5bf0fec1c0d37320847344e4242c6
-size 4940839
+oid sha256:06b4611651b627f852523ac4bb98d41a6afcbb58f307e1f605fadde832e4f186
+size 4986833
diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br
index bdab4a07dd..4d847a1a76 100644
--- a/lib/search/indexes/github-docs-ghec-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:51877679d54ac292f275f6ea5b20c7385e4ac8e818bf4bba4e7f244b56a23734
-size 770073
+oid sha256:94826df99a41604294aef65505950358db1a2e07e2707fdfba8e248e5b1db619
+size 789572
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 13fbfe8b32..243d3aa9a9 100644
--- a/lib/search/indexes/github-docs-ghec-es.json.br
+++ b/lib/search/indexes/github-docs-ghec-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:97e22e7d1817019fefc511a6787fc4643a4d42bff16cca18729e3bf3f4029e70
-size 3249454
+oid sha256:fcb3a65be4e0c52006b323980ca703dd54c2701e014e37bc8556def441265639
+size 3338892
diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br
index 16958252e5..224b6f3c0a 100644
--- a/lib/search/indexes/github-docs-ghec-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6c78bc70e84cfbee00bd9981ae9d2427e6b847a92df8b0f7c25e8ec8ddfd111b
-size 837690
+oid sha256:e3a375679c9eb7f76dde4463e5fd631d66aeb96ef614d9138be80cb9cd4d9759
+size 845992
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 3c7fbd6160..aee8757961 100644
--- a/lib/search/indexes/github-docs-ghec-ja.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:29f7331640d88e1bcd2e0548aa1529fdd09040cbca3ccd97779fbe1e4a15dc6f
-size 4479226
+oid sha256:f151b6e2629c39cc2448becee4409bb8b6211933ebe37a9a0252caf0c22f172d
+size 4501553
diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br
index 2ecafe4567..670bc8e0c0 100644
--- a/lib/search/indexes/github-docs-ghec-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c9fd436d7119565a226e19069d7bd8616da6ecfdc98a93b27a31d6d1832ecdb9
-size 759193
+oid sha256:4a6226ab00debd80ae8d6297d4a8c596bf9c9f70f4cd52c9eb2338ccacc76871
+size 776866
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 6c5d454ea7..9228cdb7e2 100644
--- a/lib/search/indexes/github-docs-ghec-pt.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bc8feae896067db3834cd3abcb224baf9fc6ef54bf57090b8699cb883fd5faac
-size 3092747
+oid sha256:6a40a3f121297d5ebdb768576caab6b3a907216fcfe2702d98f384f902d490f2
+size 3171254
diff --git a/middleware/archived-asset-redirects.js b/middleware/archived-asset-redirects.js
new file mode 100644
index 0000000000..4ca8e53a1f
--- /dev/null
+++ b/middleware/archived-asset-redirects.js
@@ -0,0 +1,28 @@
+// When we archive old versions, we take a snapshot of rendered pages,
+// which includes whatever bundles it used at the time.
+// Sometimes those archived versions don't include all static assets
+// it might refer to.
+// This middleware is a chance to redirect to new assets that we can
+// use instead.
+// Yes, not all legacy assets *can* be redirected to something we have
+// today. But for those that we can, this is the middleware to do it.
+// And the reason we don't host a copy of these old files is because
+// we strive to make the files in the repo only files that we actually
+// use and refer to in the non-archived content.
+
+// Note that, we also have `archived-enterprise-versions-assets.js`
+// but that one assumes the whole path refers to a prefix which is
+// considered archived. E.g. /en/enterprise-server@2.9/foo/bar.css
+
+const REDIRECTS = {
+  // Example: https://docs.github.com/en/enterprise-server@2.22/authentication/connecting-to-github-with-ssh
+  '/assets/images/octicons/search.svg': '/assets/images/octicons/search-24.svg',
+}
+export default function archivedAssetRedirects(req, res, next) {
+  if (req.path in REDIRECTS) {
+    const redirect = REDIRECTS[req.path].replace('/assets/', '/assets/cb-0000/')
+    return res.redirect(308, redirect)
+  }
+
+  return next()
+}
diff --git a/middleware/index.js b/middleware/index.js
index 4093c9179d..4a3951c374 100644
--- a/middleware/index.js
+++ b/middleware/index.js
@@ -13,10 +13,7 @@ import cookieParser from './cookie-parser.js'
 import csrf from './csrf.js'
 import handleCsrfErrors from './handle-csrf-errors.js'
 import compression from 'compression'
-import {
-  setDefaultFastlySurrogateKey,
-  setManualFastlySurrogateKey,
-} from './set-fastly-surrogate-key.js'
+import { setDefaultFastlySurrogateKey } from './set-fastly-surrogate-key.js'
 import setFastlyCacheHeaders from './set-fastly-cache-headers.js'
 import catchBadAcceptLanguage from './catch-bad-accept-language.js'
 import reqUtils from './req-utils.js'
@@ -61,7 +58,9 @@ import learningTrack from './learning-track.js'
 import next from './next.js'
 import renderPage from './render-page.js'
 import assetPreprocessing from './asset-preprocessing.js'
+import archivedAssetRedirects from './archived-asset-redirects.js'
 import favicon from './favicon.js'
+import setStaticAssetCaching from './static-asset-caching.js'
 
 const { DEPLOYMENT_ENV, NODE_ENV } = process.env
 const isDevelopment = NODE_ENV === 'development'
@@ -114,12 +113,23 @@ export default function (app) {
 
   app.use(favicon)
 
+  // Any static URL that contains some sort of checksum that makes it
+  // unique gets the "manual" surrogate key. If it's checksummed,
+  // it's bound to change when it needs to change. Otherwise,
+  // we want to make sure it doesn't need to be purged just because
+  // there's a production deploy.
+  // Note, for `/assets/cb-*...` requests,
+  // this needs to come before `assetPreprocessing` because
+  // the `assetPreprocessing` middleware will rewrite `req.url` if
+  // it applies.
+  app.use(setStaticAssetCaching)
+
+  // Must come before any other middleware for assets
+  app.use(archivedAssetRedirects)
+
   // This must come before the express.static('assets') middleware.
   app.use(assetPreprocessing)
-  // By specifying '/assets/cb-' and not just '/assets/' we
-  // avoid possibly legacy enterprise assets URLs and asset image URLs
-  // that don't have the cache-busting piece in it.
-  app.use('/assets/cb-', setManualFastlySurrogateKey)
+
   app.use(
     '/assets/',
     express.static('assets', {
diff --git a/middleware/set-fastly-surrogate-key.js b/middleware/set-fastly-surrogate-key.js
index 6bfc457423..002d3f521d 100644
--- a/middleware/set-fastly-surrogate-key.js
+++ b/middleware/set-fastly-surrogate-key.js
@@ -23,11 +23,6 @@ export function setFastlySurrogateKey(res, enumKey) {
   res.set(KEY, enumKey)
 }
 
-export function setManualFastlySurrogateKey(req, res, next) {
-  res.set(KEY, SURROGATE_ENUMS.MANUAL)
-  return next()
-}
-
 export function setDefaultFastlySurrogateKey(req, res, next) {
   res.set(KEY, SURROGATE_ENUMS.DEFAULT)
   return next()
diff --git a/middleware/static-asset-caching.js b/middleware/static-asset-caching.js
new file mode 100644
index 0000000000..35126f70f1
--- /dev/null
+++ b/middleware/static-asset-caching.js
@@ -0,0 +1,16 @@
+import { setFastlySurrogateKey, SURROGATE_ENUMS } from './set-fastly-surrogate-key.js'
+
+export default function setStaticAssetCaching(req, res, next) {
+  if (isChecksummed(req.path)) {
+    setFastlySurrogateKey(res, SURROGATE_ENUMS.MANUAL)
+  }
+  return next()
+}
+
+// True if the URL is known to contain some pattern of a checksum that
+// would make it intelligently different if its content has changed.
+function isChecksummed(path) {
+  if (path.startsWith('/assets/cb-')) return true
+  if (path.startsWith('/_next/static') && /[a-f0-9]{20}/.test(path)) return true
+  return false
+}
diff --git a/package-lock.json b/package-lock.json
index d892291719..7f02ab473f 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -85,7 +85,6 @@
         "strip-html-comments": "^1.0.0",
         "styled-components": "^5.3.3",
         "swr": "1.1.2",
-        "throng": "^5.0.0",
         "ts-dedent": "^2.2.0",
         "unified": "^10.1.0",
         "unist-util-visit": "^4.1.0",
@@ -164,10 +163,9 @@
         "sass": "^1.49.0",
         "start-server-and-test": "^1.14.0",
         "strip-ansi": "^7.0.1",
-        "supertest": "^6.1.6",
+        "supertest": "^6.2.2",
         "typescript": "^4.5.5",
-        "url-template": "^3.0.0",
-        "yesno": "^0.3.1"
+        "url-template": "^3.0.0"
       },
       "engines": {
         "node": "16.x"
@@ -181,7 +179,7 @@
         "jimp": "^0.16.1",
         "pa11y-ci": "^2.4.2",
         "puppeteer": "^9.1.1",
-        "website-scraper": "^4.2.3",
+        "website-scraper": "^5.0.0",
         "xlsx-populate": "^1.21.0"
       }
     },
@@ -4876,14 +4874,11 @@
         "node": ">=0.10.0"
       }
     },
-    "node_modules/asn1": {
-      "version": "0.2.6",
-      "resolved": "https://registry.npmjs.org/asn1/-/asn1-0.2.6.tgz",
-      "integrity": "sha512-ix/FxPn0MDjeyJ7i/yoHGFt/EX6LyNbxSEhPPXODPL+KB0VPk86UYfL0lMdy+KCnv+fmvIzySwaK5COwqVbWTQ==",
-      "optional": true,
-      "dependencies": {
-        "safer-buffer": "~2.1.0"
-      }
+    "node_modules/asap": {
+      "version": "2.0.6",
+      "resolved": "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz",
+      "integrity": "sha1-5QNHYR1+aQlDIIu9r+vLwvuGbUY=",
+      "dev": true
     },
     "node_modules/asn1.js": {
       "version": "5.4.1",
@@ -4912,15 +4907,6 @@
         "util": "^0.12.0"
       }
     },
-    "node_modules/assert-plus": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-1.0.0.tgz",
-      "integrity": "sha1-8S4PPF13sLHN2RRpQuTpbB5N1SU=",
-      "optional": true,
-      "engines": {
-        "node": ">=0.8"
-      }
-    },
     "node_modules/ast-types": {
       "version": "0.13.2",
       "resolved": "https://registry.npmjs.org/ast-types/-/ast-types-0.13.2.tgz",
@@ -4960,7 +4946,7 @@
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
       "integrity": "sha1-x57Zf380y48robyXkLzDZkdLS3k=",
-      "devOptional": true
+      "dev": true
     },
     "node_modules/available-typed-arrays": {
       "version": "1.0.5",
@@ -4973,21 +4959,6 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/aws-sign2": {
-      "version": "0.7.0",
-      "resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.7.0.tgz",
-      "integrity": "sha1-tG6JCTSpWR8tL2+G1+ap8bP+dqg=",
-      "optional": true,
-      "engines": {
-        "node": "*"
-      }
-    },
-    "node_modules/aws4": {
-      "version": "1.11.0",
-      "resolved": "https://registry.npmjs.org/aws4/-/aws4-1.11.0.tgz",
-      "integrity": "sha512-xh1Rl34h6Fi1DC2WWKfxUTVqRsNnr6LsKz2+hfwDxQJWmrx8+c7ylaqBMcHfl1U1r2dsifOvKX3LQuLNZ+XSvA==",
-      "optional": true
-    },
     "node_modules/axe-core": {
       "version": "4.3.5",
       "resolved": "https://registry.npmjs.org/axe-core/-/axe-core-4.3.5.tgz",
@@ -5368,13 +5339,13 @@
       }
     },
     "node_modules/babel-plugin-polyfill-corejs3": {
-      "version": "0.5.2",
-      "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.2.tgz",
-      "integrity": "sha512-G3uJih0XWiID451fpeFaYGVuxHEjzKTHtc9uGFEjR6hHrvNzeS/PX+LLLcetJcytsB5m4j+K3o/EpXJNb/5IEQ==",
+      "version": "0.5.1",
+      "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.1.tgz",
+      "integrity": "sha512-TihqEe4sQcb/QcPJvxe94/9RZuLQuF1+To4WqQcRvc+3J3gLCPIPgDKzGLG6zmQLfH3nn25heRuDNkS2KR4I8A==",
       "dev": true,
       "dependencies": {
         "@babel/helper-define-polyfill-provider": "^0.3.1",
-        "core-js-compat": "^3.21.0"
+        "core-js-compat": "^3.20.0"
       },
       "peerDependencies": {
         "@babel/core": "^7.0.0-0"
@@ -6005,15 +5976,6 @@
         "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/bcrypt-pbkdf": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.2.tgz",
-      "integrity": "sha1-pDAdOJtqQ/m2f/PKEaP2Y342Dp4=",
-      "optional": true,
-      "dependencies": {
-        "tweetnacl": "^0.14.3"
-      }
-    },
     "node_modules/before-after-hook": {
       "version": "2.2.2",
       "resolved": "https://registry.npmjs.org/before-after-hook/-/before-after-hook-2.2.2.tgz",
@@ -6065,7 +6027,7 @@
       "version": "3.7.2",
       "resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.7.2.tgz",
       "integrity": "sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==",
-      "devOptional": true
+      "dev": true
     },
     "node_modules/bmp-js": {
       "version": "0.1.0",
@@ -6529,18 +6491,6 @@
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/camelcase-keys/node_modules/quick-lru": {
-      "version": "5.1.1",
-      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
-      "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
-      "dev": true,
-      "engines": {
-        "node": ">=10"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
     "node_modules/camelcase-keys/node_modules/type-fest": {
       "version": "1.4.0",
       "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
@@ -6578,12 +6528,6 @@
         "upper-case-first": "^2.0.2"
       }
     },
-    "node_modules/caseless": {
-      "version": "0.12.0",
-      "resolved": "https://registry.npmjs.org/caseless/-/caseless-0.12.0.tgz",
-      "integrity": "sha1-G2gcIf+EAzyCZUMJBolCDRhxUdw=",
-      "optional": true
-    },
     "node_modules/ccount": {
       "version": "2.0.0",
       "resolved": "https://registry.npmjs.org/ccount/-/ccount-2.0.0.tgz",
@@ -7014,7 +6958,7 @@
       "version": "1.0.8",
       "resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.8.tgz",
       "integrity": "sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==",
-      "devOptional": true,
+      "dev": true,
       "dependencies": {
         "delayed-stream": "~1.0.0"
       },
@@ -7298,9 +7242,9 @@
       "hasInstallScript": true
     },
     "node_modules/core-js-compat": {
-      "version": "3.21.0",
-      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.21.0.tgz",
-      "integrity": "sha512-OSXseNPSK2OPJa6GdtkMz/XxeXx8/CJvfhQWTqd6neuUraujcL4jVsjkLQz1OWnax8xVQJnRPe0V2jqNWORA+A==",
+      "version": "3.20.2",
+      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.20.2.tgz",
+      "integrity": "sha512-qZEzVQ+5Qh6cROaTPFLNS4lkvQ6mBzE3R6A6EEpssj7Zr2egMHgsy4XapdifqJDGC9CBiNv7s+ejI96rLNQFdg==",
       "dev": true,
       "dependencies": {
         "browserslist": "^4.19.1",
@@ -7612,18 +7556,6 @@
       "integrity": "sha512-VvdQIPGdWP0SqFXghj79Wf/5LArmreyMsGLa6FG6iC4t3j7j5s71TrwWmT/4akbDQIqjfACkLZmjXhA7g2oUZw==",
       "dev": true
     },
-    "node_modules/dashdash": {
-      "version": "1.14.1",
-      "resolved": "https://registry.npmjs.org/dashdash/-/dashdash-1.14.1.tgz",
-      "integrity": "sha1-hTz6D3y+L+1d4gMmuN1YEDX24vA=",
-      "optional": true,
-      "dependencies": {
-        "assert-plus": "^1.0.0"
-      },
-      "engines": {
-        "node": ">=0.10"
-      }
-    },
     "node_modules/data-uri-to-buffer": {
       "version": "3.0.1",
       "resolved": "https://registry.npmjs.org/data-uri-to-buffer/-/data-uri-to-buffer-3.0.1.tgz",
@@ -7800,7 +7732,7 @@
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
       "integrity": "sha1-3zrhmayt+31ECqrgsp4icrJOxhk=",
-      "devOptional": true,
+      "dev": true,
       "engines": {
         "node": ">=0.4.0"
       }
@@ -7873,6 +7805,16 @@
       "integrity": "sha512-VvlVYY+VDJe639yHs5PHISzdWTLL3Aw8rO4cvUtwvoxFd6FHbE4OpHHcde52M6096uYYazAmd4l0o5VuFRO2WA==",
       "optional": true
     },
+    "node_modules/dezalgo": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/dezalgo/-/dezalgo-1.0.3.tgz",
+      "integrity": "sha1-f3Qt4Gb8dIvI24IFad3c5Jvw1FY=",
+      "dev": true,
+      "dependencies": {
+        "asap": "^2.0.0",
+        "wrappy": "1"
+      }
+    },
     "node_modules/diff": {
       "version": "5.0.0",
       "resolved": "https://registry.npmjs.org/diff/-/diff-5.0.0.tgz",
@@ -8182,16 +8124,6 @@
       "integrity": "sha1-7gHdHKwO08vH/b6jfcCo8c4ALOI=",
       "dev": true
     },
-    "node_modules/ecc-jsbn": {
-      "version": "0.1.2",
-      "resolved": "https://registry.npmjs.org/ecc-jsbn/-/ecc-jsbn-0.1.2.tgz",
-      "integrity": "sha1-OoOpBOVDUyh4dMVkt1SThoSamMk=",
-      "optional": true,
-      "dependencies": {
-        "jsbn": "~0.1.0",
-        "safer-buffer": "^2.1.0"
-      }
-    },
     "node_modules/ee-first": {
       "version": "1.1.1",
       "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
@@ -9369,15 +9301,6 @@
         "@types/yauzl": "^2.9.1"
       }
     },
-    "node_modules/extsprintf": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.3.0.tgz",
-      "integrity": "sha1-lpGEQOMEGnpBT4xS48V06zw+HgU=",
-      "engines": [
-        "node >=0.6.0"
-      ],
-      "optional": true
-    },
     "node_modules/fast-deep-equal": {
       "version": "3.1.3",
       "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
@@ -9720,15 +9643,6 @@
       "resolved": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz",
       "integrity": "sha1-C+4AUBiusmDQo6865ljdATbsG5k="
     },
-    "node_modules/forever-agent": {
-      "version": "0.6.1",
-      "resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
-      "integrity": "sha1-+8cfDEGt6zf5bFd60e1C2P2sypE=",
-      "optional": true,
-      "engines": {
-        "node": "*"
-      }
-    },
     "node_modules/form-data": {
       "version": "3.0.1",
       "resolved": "https://registry.npmjs.org/form-data/-/form-data-3.0.1.tgz",
@@ -9743,6 +9657,12 @@
         "node": ">= 6"
       }
     },
+    "node_modules/form-data-encoder": {
+      "version": "1.7.1",
+      "resolved": "https://registry.npmjs.org/form-data-encoder/-/form-data-encoder-1.7.1.tgz",
+      "integrity": "sha512-EFRDrsMm/kyqbTQocNvRXMLjc7Es2Vk+IQFx/YW7hkUH1eBl4J1fqiP34l74Yt0pFLCNpc06fkbVk00008mzjg==",
+      "optional": true
+    },
     "node_modules/format": {
       "version": "0.2.2",
       "resolved": "https://registry.npmjs.org/format/-/format-0.2.2.tgz",
@@ -9763,14 +9683,32 @@
       }
     },
     "node_modules/formidable": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/formidable/-/formidable-1.2.2.tgz",
-      "integrity": "sha512-V8gLm+41I/8kguQ4/o1D3RIHRmhYFG4pnNyonvua+40rqcEmT4+V71yaZ3B457xbbgCsCfjSPi65u/W6vK1U5Q==",
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/formidable/-/formidable-2.0.1.tgz",
+      "integrity": "sha512-rjTMNbp2BpfQShhFbR3Ruk3qk2y9jKpvMW78nJgx8QKtxjDVrwbZG+wvDOmVbifHyOUOQJXxqEy6r0faRrPzTQ==",
       "dev": true,
+      "dependencies": {
+        "dezalgo": "1.0.3",
+        "hexoid": "1.0.0",
+        "once": "1.4.0",
+        "qs": "6.9.3"
+      },
       "funding": {
         "url": "https://ko-fi.com/tunnckoCore/commissions"
       }
     },
+    "node_modules/formidable/node_modules/qs": {
+      "version": "6.9.3",
+      "resolved": "https://registry.npmjs.org/qs/-/qs-6.9.3.tgz",
+      "integrity": "sha512-EbZYNarm6138UKKq46tdx08Yo/q9ZhFoAXAI1meAFd2GtbRDhbZY2WQSICskT0c5q99aFzLG1D4nvTk9tqfXIw==",
+      "dev": true,
+      "engines": {
+        "node": ">=0.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
     "node_modules/forwarded": {
       "version": "0.2.0",
       "resolved": "https://registry.npmjs.org/forwarded/-/forwarded-0.2.0.tgz",
@@ -9809,17 +9747,26 @@
       }
     },
     "node_modules/fs-extra": {
-      "version": "8.1.0",
-      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz",
-      "integrity": "sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==",
+      "version": "10.0.0",
+      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.0.0.tgz",
+      "integrity": "sha512-C5owb14u9eJwizKGdchcDUQeFtlSHHthBk8pbX9Vc1PFZrLombudjDnNns88aYslCyF6IY5SUw3Roz6xShcEIQ==",
       "optional": true,
       "dependencies": {
         "graceful-fs": "^4.2.0",
-        "jsonfile": "^4.0.0",
-        "universalify": "^0.1.0"
+        "jsonfile": "^6.0.1",
+        "universalify": "^2.0.0"
       },
       "engines": {
-        "node": ">=6 <7 || >=8"
+        "node": ">=12"
+      }
+    },
+    "node_modules/fs-extra/node_modules/universalify": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
+      "integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==",
+      "optional": true,
+      "engines": {
+        "node": ">= 10.0.0"
       }
     },
     "node_modules/fs.realpath": {
@@ -9978,15 +9925,6 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/getpass": {
-      "version": "0.1.7",
-      "resolved": "https://registry.npmjs.org/getpass/-/getpass-0.1.7.tgz",
-      "integrity": "sha1-Xv+OPmhNVprkyysSgmBOi6YhSfo=",
-      "optional": true,
-      "dependencies": {
-        "assert-plus": "^1.0.0"
-      }
-    },
     "node_modules/gifwrap": {
       "version": "0.9.2",
       "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.2.tgz",
@@ -10317,51 +10255,6 @@
         "js-yaml": "bin/js-yaml.js"
       }
     },
-    "node_modules/har-schema": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/har-schema/-/har-schema-2.0.0.tgz",
-      "integrity": "sha1-qUwiJOvKwEeCoNkDVSHyRzW37JI=",
-      "optional": true,
-      "engines": {
-        "node": ">=4"
-      }
-    },
-    "node_modules/har-validator": {
-      "version": "5.1.5",
-      "resolved": "https://registry.npmjs.org/har-validator/-/har-validator-5.1.5.tgz",
-      "integrity": "sha512-nmT2T0lljbxdQZfspsno9hgrG3Uir6Ks5afism62poxqBM6sDnMEuPmzTq8XN0OEwqKLLdh1jQI3qyE66Nzb3w==",
-      "deprecated": "this library is no longer supported",
-      "optional": true,
-      "dependencies": {
-        "ajv": "^6.12.3",
-        "har-schema": "^2.0.0"
-      },
-      "engines": {
-        "node": ">=6"
-      }
-    },
-    "node_modules/har-validator/node_modules/ajv": {
-      "version": "6.12.6",
-      "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
-      "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
-      "optional": true,
-      "dependencies": {
-        "fast-deep-equal": "^3.1.1",
-        "fast-json-stable-stringify": "^2.0.0",
-        "json-schema-traverse": "^0.4.1",
-        "uri-js": "^4.2.2"
-      },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/epoberezkin"
-      }
-    },
-    "node_modules/har-validator/node_modules/json-schema-traverse": {
-      "version": "0.4.1",
-      "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
-      "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
-      "optional": true
-    },
     "node_modules/hard-rejection": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/hard-rejection/-/hard-rejection-2.1.0.tgz",
@@ -10754,6 +10647,15 @@
         "node": ">=6.0.0"
       }
     },
+    "node_modules/hexoid": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz",
+      "integrity": "sha512-QFLV0taWQOZtvIRIAdBChesmogZrtuXvVWsFHZTk2SU+anspqZ2vMnoLg7IE1+Uk16N19APic1BuF8bC8c2m5g==",
+      "dev": true,
+      "engines": {
+        "node": ">=8"
+      }
+    },
     "node_modules/highlight.js": {
       "version": "11.2.0",
       "resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-11.2.0.tgz",
@@ -10927,21 +10829,6 @@
         "node": ">= 6"
       }
     },
-    "node_modules/http-signature": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/http-signature/-/http-signature-1.2.0.tgz",
-      "integrity": "sha1-muzZJRFHcvPZW2WmCruPfBj7rOE=",
-      "optional": true,
-      "dependencies": {
-        "assert-plus": "^1.0.0",
-        "jsprim": "^1.2.2",
-        "sshpk": "^1.7.0"
-      },
-      "engines": {
-        "node": ">=0.8",
-        "npm": ">=1.3.7"
-      }
-    },
     "node_modules/http-status-code": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/http-status-code/-/http-status-code-2.1.0.tgz",
@@ -10975,17 +10862,6 @@
         "node": ">=10.19.0"
       }
     },
-    "node_modules/http2-wrapper/node_modules/quick-lru": {
-      "version": "5.1.1",
-      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
-      "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
-      "engines": {
-        "node": ">=10"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
     "node_modules/https-browserify": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/https-browserify/-/https-browserify-1.0.0.tgz",
@@ -11694,7 +11570,7 @@
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/is-typedarray/-/is-typedarray-1.0.0.tgz",
       "integrity": "sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=",
-      "devOptional": true
+      "dev": true
     },
     "node_modules/is-url": {
       "version": "1.2.4",
@@ -11778,12 +11654,6 @@
         "node": ">=0.10.0"
       }
     },
-    "node_modules/isstream": {
-      "version": "0.1.2",
-      "resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
-      "integrity": "sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=",
-      "optional": true
-    },
     "node_modules/istanbul-lib-coverage": {
       "version": "3.2.0",
       "resolved": "https://registry.npmjs.org/istanbul-lib-coverage/-/istanbul-lib-coverage-3.2.0.tgz",
@@ -12921,12 +12791,6 @@
         "js-yaml": "bin/js-yaml.js"
       }
     },
-    "node_modules/jsbn": {
-      "version": "0.1.1",
-      "resolved": "https://registry.npmjs.org/jsbn/-/jsbn-0.1.1.tgz",
-      "integrity": "sha1-peZUwuWi3rXyAdls77yoDA7y9RM=",
-      "optional": true
-    },
     "node_modules/jsdom": {
       "version": "16.7.0",
       "resolved": "https://registry.npmjs.org/jsdom/-/jsdom-16.7.0.tgz",
@@ -13014,12 +12878,6 @@
       "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==",
       "dev": true
     },
-    "node_modules/json-schema": {
-      "version": "0.4.0",
-      "resolved": "https://registry.npmjs.org/json-schema/-/json-schema-0.4.0.tgz",
-      "integrity": "sha512-es94M3nTIfsEPisRafak+HDLfHXnKBhV3vU5eqPcS3flIWqcxJWgXHXiey3YrpaNsanY5ei1VoYEbOzijuq9BA==",
-      "optional": true
-    },
     "node_modules/json-schema-traverse": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
@@ -13035,7 +12893,7 @@
       "version": "5.0.1",
       "resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
       "integrity": "sha1-Epai1Y/UXxmg9s4B1lcB4sc1tus=",
-      "devOptional": true
+      "dev": true
     },
     "node_modules/json5": {
       "version": "2.2.0",
@@ -13061,27 +12919,24 @@
       }
     },
     "node_modules/jsonfile": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz",
-      "integrity": "sha1-h3Gq4HmbZAdrdmQPygWPnBDjPss=",
+      "version": "6.1.0",
+      "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
+      "integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
       "optional": true,
+      "dependencies": {
+        "universalify": "^2.0.0"
+      },
       "optionalDependencies": {
         "graceful-fs": "^4.1.6"
       }
     },
-    "node_modules/jsprim": {
-      "version": "1.4.2",
-      "resolved": "https://registry.npmjs.org/jsprim/-/jsprim-1.4.2.tgz",
-      "integrity": "sha512-P2bSOMAc/ciLz6DzgjVlGJP9+BrJWu5UDGK70C2iweC5QBIeFf0ZXRvGjEj2uYgrY2MkAAhsSWHDWlFtEroZWw==",
+    "node_modules/jsonfile/node_modules/universalify": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
+      "integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==",
       "optional": true,
-      "dependencies": {
-        "assert-plus": "1.0.0",
-        "extsprintf": "1.3.0",
-        "json-schema": "0.4.0",
-        "verror": "1.10.0"
-      },
       "engines": {
-        "node": ">=0.6.0"
+        "node": ">= 10.0.0"
       }
     },
     "node_modules/jsx-ast-utils": {
@@ -13565,18 +13420,6 @@
       "resolved": "https://registry.npmjs.org/lodash-es/-/lodash-es-4.17.21.tgz",
       "integrity": "sha512-mKnC+QJ9pWVzv+C4/U3rRsHapFfHvQFoFB92e52xeyGMcX6/OlIl78je1u8vePzYZSkkogMPJ2yjxxsb89cxyw=="
     },
-    "node_modules/lodash.assignin": {
-      "version": "4.2.0",
-      "resolved": "https://registry.npmjs.org/lodash.assignin/-/lodash.assignin-4.2.0.tgz",
-      "integrity": "sha1-uo31+4QesKPoBEIysOJjqNxqKKI=",
-      "optional": true
-    },
-    "node_modules/lodash.bind": {
-      "version": "4.2.1",
-      "resolved": "https://registry.npmjs.org/lodash.bind/-/lodash.bind-4.2.1.tgz",
-      "integrity": "sha1-euMBfpOWIqwxt9fX3LGzTbFpDTU=",
-      "optional": true
-    },
     "node_modules/lodash.clonedeep": {
       "version": "4.5.0",
       "resolved": "https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz",
@@ -13589,59 +13432,11 @@
       "integrity": "sha1-gteb/zCmfEAF/9XiUVMArZyk168=",
       "dev": true
     },
-    "node_modules/lodash.defaults": {
-      "version": "4.2.0",
-      "resolved": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-4.2.0.tgz",
-      "integrity": "sha1-0JF4cW/+pN3p5ft7N/bwgCJ0WAw=",
-      "optional": true
-    },
-    "node_modules/lodash.filter": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.filter/-/lodash.filter-4.6.0.tgz",
-      "integrity": "sha1-ZosdSYFgOuHMWm+nYBQ+SAtMSs4=",
-      "optional": true
-    },
-    "node_modules/lodash.flatten": {
-      "version": "4.4.0",
-      "resolved": "https://registry.npmjs.org/lodash.flatten/-/lodash.flatten-4.4.0.tgz",
-      "integrity": "sha1-8xwiIlqWMtK7+OSt2+8kCqdlph8=",
-      "optional": true
-    },
-    "node_modules/lodash.foreach": {
-      "version": "4.5.0",
-      "resolved": "https://registry.npmjs.org/lodash.foreach/-/lodash.foreach-4.5.0.tgz",
-      "integrity": "sha1-Gmo16s5AEoDH8G3d7DUWWrJ+PlM=",
-      "optional": true
-    },
-    "node_modules/lodash.map": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.map/-/lodash.map-4.6.0.tgz",
-      "integrity": "sha1-dx7Hg540c9nEzeKLGTlMNWL09tM=",
-      "optional": true
-    },
     "node_modules/lodash.merge": {
       "version": "4.6.2",
       "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
       "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
-      "devOptional": true
-    },
-    "node_modules/lodash.pick": {
-      "version": "4.4.0",
-      "resolved": "https://registry.npmjs.org/lodash.pick/-/lodash.pick-4.4.0.tgz",
-      "integrity": "sha1-UvBWEP/53tQiYRRB7R/BI6AwAbM=",
-      "optional": true
-    },
-    "node_modules/lodash.reduce": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.reduce/-/lodash.reduce-4.6.0.tgz",
-      "integrity": "sha1-8atrg5KZrUj3hKu/R2WW8DuRTTs=",
-      "optional": true
-    },
-    "node_modules/lodash.reject": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.reject/-/lodash.reject-4.6.0.tgz",
-      "integrity": "sha1-gNZJLcFHCGS79YNTO2UfQqn1JBU=",
-      "optional": true
+      "dev": true
     },
     "node_modules/lodash.set": {
       "version": "4.3.2",
@@ -13649,12 +13444,6 @@
       "integrity": "sha1-2HV7HagH3eJIFrDWqEvqGnYjCyM=",
       "dev": true
     },
-    "node_modules/lodash.some": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.some/-/lodash.some-4.6.0.tgz",
-      "integrity": "sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=",
-      "optional": true
-    },
     "node_modules/lodash.sortby": {
       "version": "4.7.0",
       "resolved": "https://registry.npmjs.org/lodash.sortby/-/lodash.sortby-4.7.0.tgz",
@@ -16025,15 +15814,6 @@
       "integrity": "sha512-h2AatdwYH+JHiZpv7pt/gSX1XoRGb7L/qSIeuqA6GwYoF9w1vP1cw42TO0aI2pNyshRK5893hNSl+1//vHK7hQ==",
       "dev": true
     },
-    "node_modules/oauth-sign": {
-      "version": "0.9.0",
-      "resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.9.0.tgz",
-      "integrity": "sha512-fexhUFFPTGV8ybAtSIGbV6gOkSv8UtRbDBnAyLQw4QPKkgNlsH2ByPGtMUqdWkos6YCRmAqViwgZrJc/mRDzZQ==",
-      "optional": true,
-      "engines": {
-        "node": "*"
-      }
-    },
     "node_modules/object-assign": {
       "version": "4.1.1",
       "resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
@@ -16293,31 +16073,31 @@
       }
     },
     "node_modules/p-queue": {
-      "version": "6.6.2",
-      "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-6.6.2.tgz",
-      "integrity": "sha512-RwFpb72c/BhQLEXIZ5K2e+AhgNVmIejGlTgiB9MzZ0e93GRvqZ7uSi0dvRF7/XIXDeNkra2fNHBxTyPDGySpjQ==",
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-7.2.0.tgz",
+      "integrity": "sha512-Kvv7p13M46lTYLQ/PsZdaj/1Vj6u/8oiIJgyQyx4oVkOfHdd7M2EZvXigDvcsSzRwanCzQirV5bJPQFoSQt5MA==",
       "optional": true,
       "dependencies": {
-        "eventemitter3": "^4.0.4",
-        "p-timeout": "^3.2.0"
+        "eventemitter3": "^4.0.7",
+        "p-timeout": "^5.0.2"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/p-queue/node_modules/p-timeout": {
-      "version": "3.2.0",
-      "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-3.2.0.tgz",
-      "integrity": "sha512-rhIwUycgwwKcP9yTOOFK/AKsAopjjCakVqLHePO3CC6Mir1Z99xT+R63jZxAT5lFZLa2inS5h+ZS2GvR99/FBg==",
+      "version": "5.0.2",
+      "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-5.0.2.tgz",
+      "integrity": "sha512-sEmji9Yaq+Tw+STwsGAE56hf7gMy9p0tQfJojIAamB7WHJYJKf1qlsg9jqBWG8q9VCxKPhZaP/AcXwEoBcYQhQ==",
       "optional": true,
-      "dependencies": {
-        "p-finally": "^1.0.0"
-      },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/p-timeout": {
@@ -17344,12 +17124,6 @@
       "integrity": "sha1-elfrVQpng/kRUzH89GY9XI4AelA=",
       "optional": true
     },
-    "node_modules/performance-now": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/performance-now/-/performance-now-2.1.0.tgz",
-      "integrity": "sha1-Ywn04OX6kT7BxpMHrjZLSzd8nns=",
-      "optional": true
-    },
     "node_modules/phin": {
       "version": "2.9.3",
       "resolved": "https://registry.npmjs.org/phin/-/phin-2.9.3.tgz",
@@ -17755,7 +17529,7 @@
       "version": "1.8.0",
       "resolved": "https://registry.npmjs.org/psl/-/psl-1.8.0.tgz",
       "integrity": "sha512-RIdOzyoavK+hA18OGGWDqUTsCLhtA7IcZ/6NCs4fFJaHBDab+pDDmDIByWFRQJq2Cd7r1OoQxBGKOaztq+hjIQ==",
-      "devOptional": true
+      "dev": true
     },
     "node_modules/pstree.remy": {
       "version": "1.1.8",
@@ -17933,6 +17707,17 @@
         }
       ]
     },
+    "node_modules/quick-lru": {
+      "version": "5.1.1",
+      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
+      "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
     "node_modules/random-bytes": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/random-bytes/-/random-bytes-1.0.0.tgz",
@@ -19230,84 +19015,6 @@
         "node": ">=6"
       }
     },
-    "node_modules/request": {
-      "version": "2.88.2",
-      "resolved": "https://registry.npmjs.org/request/-/request-2.88.2.tgz",
-      "integrity": "sha512-MsvtOrfG9ZcrOwAW+Qi+F6HbD0CWXEh9ou77uOb7FM2WPhwT7smM833PzanhJLsgXjN89Ir6V2PczXNnMpwKhw==",
-      "deprecated": "request has been deprecated, see https://github.com/request/request/issues/3142",
-      "optional": true,
-      "dependencies": {
-        "aws-sign2": "~0.7.0",
-        "aws4": "^1.8.0",
-        "caseless": "~0.12.0",
-        "combined-stream": "~1.0.6",
-        "extend": "~3.0.2",
-        "forever-agent": "~0.6.1",
-        "form-data": "~2.3.2",
-        "har-validator": "~5.1.3",
-        "http-signature": "~1.2.0",
-        "is-typedarray": "~1.0.0",
-        "isstream": "~0.1.2",
-        "json-stringify-safe": "~5.0.1",
-        "mime-types": "~2.1.19",
-        "oauth-sign": "~0.9.0",
-        "performance-now": "^2.1.0",
-        "qs": "~6.5.2",
-        "safe-buffer": "^5.1.2",
-        "tough-cookie": "~2.5.0",
-        "tunnel-agent": "^0.6.0",
-        "uuid": "^3.3.2"
-      },
-      "engines": {
-        "node": ">= 6"
-      }
-    },
-    "node_modules/request/node_modules/form-data": {
-      "version": "2.3.3",
-      "resolved": "https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz",
-      "integrity": "sha512-1lLKB2Mu3aGP1Q/2eCOx0fNbRMe7XdwktwOruhfqqd0rIJWwN4Dh+E3hrPSlDCXnSR7UtZ1N38rVXm+6+MEhJQ==",
-      "optional": true,
-      "dependencies": {
-        "asynckit": "^0.4.0",
-        "combined-stream": "^1.0.6",
-        "mime-types": "^2.1.12"
-      },
-      "engines": {
-        "node": ">= 0.12"
-      }
-    },
-    "node_modules/request/node_modules/qs": {
-      "version": "6.5.3",
-      "resolved": "https://registry.npmjs.org/qs/-/qs-6.5.3.tgz",
-      "integrity": "sha512-qxXIEh4pCGfHICj1mAJQ2/2XVZkjCDTcEgfoSQxc/fYivUZxTkk7L3bDBJSoNrEzXI17oUO5Dp07ktqE5KzczA==",
-      "optional": true,
-      "engines": {
-        "node": ">=0.6"
-      }
-    },
-    "node_modules/request/node_modules/tough-cookie": {
-      "version": "2.5.0",
-      "resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.5.0.tgz",
-      "integrity": "sha512-nlLsUzgm1kfLXSXfRZMc1KLAugd4hqJHDTvc2hDIwS3mZAfMEuMbc03SujMF+GEcpaX/qboeycw6iO8JwVv2+g==",
-      "optional": true,
-      "dependencies": {
-        "psl": "^1.1.28",
-        "punycode": "^2.1.1"
-      },
-      "engines": {
-        "node": ">=0.8"
-      }
-    },
-    "node_modules/request/node_modules/uuid": {
-      "version": "3.4.0",
-      "resolved": "https://registry.npmjs.org/uuid/-/uuid-3.4.0.tgz",
-      "integrity": "sha512-HjSDRw6gZE5JMggctHBcjVak08+KEVhSIiDzFnT9S9aegmp85S/bReBVTb4QTFaRNptJ9kuYaNhnbNEOkbKb/A==",
-      "deprecated": "Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.",
-      "optional": true,
-      "bin": {
-        "uuid": "bin/uuid"
-      }
-    },
     "node_modules/require-directory": {
       "version": "2.1.1",
       "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
@@ -20158,37 +19865,15 @@
       "integrity": "sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw="
     },
     "node_modules/srcset": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/srcset/-/srcset-2.0.1.tgz",
-      "integrity": "sha512-00kZI87TdRKwt+P8jj8UZxbfp7mK2ufxcIMWvhAOZNJTRROimpHeruWrGvCZneiuVDLqdyHefVp748ECTnyUBQ==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/srcset/-/srcset-5.0.0.tgz",
+      "integrity": "sha512-SqEZaAEhe0A6ETEa9O1IhSPC7MdvehZtCnTR0AftXk3QhY2UNgb+NApFOUPZILXk/YTDfFxMTNJOBpzrJsEdIA==",
       "optional": true,
       "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/sshpk": {
-      "version": "1.17.0",
-      "resolved": "https://registry.npmjs.org/sshpk/-/sshpk-1.17.0.tgz",
-      "integrity": "sha512-/9HIEs1ZXGhSPE8X6Ccm7Nam1z8KcoCqPdI7ecm1N33EzAetWahvQWVqLZtaZQ+IDKX4IyA2o0gBzqIMkAagHQ==",
-      "optional": true,
-      "dependencies": {
-        "asn1": "~0.2.3",
-        "assert-plus": "^1.0.0",
-        "bcrypt-pbkdf": "^1.0.0",
-        "dashdash": "^1.12.0",
-        "ecc-jsbn": "~0.1.1",
-        "getpass": "^0.1.1",
-        "jsbn": "~0.1.0",
-        "safer-buffer": "^2.0.2",
-        "tweetnacl": "~0.14.0"
+        "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
       },
-      "bin": {
-        "sshpk-conv": "bin/sshpk-conv",
-        "sshpk-sign": "bin/sshpk-sign",
-        "sshpk-verify": "bin/sshpk-verify"
-      },
-      "engines": {
-        "node": ">=0.10.0"
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/stack-utils": {
@@ -20751,31 +20436,62 @@
       }
     },
     "node_modules/superagent": {
-      "version": "6.1.0",
-      "resolved": "https://registry.npmjs.org/superagent/-/superagent-6.1.0.tgz",
-      "integrity": "sha512-OUDHEssirmplo3F+1HWKUrUjvnQuA+nZI6i/JJBdXb5eq9IyEQwPyPpqND+SSsxf6TygpBEkUjISVRN4/VOpeg==",
+      "version": "7.1.1",
+      "resolved": "https://registry.npmjs.org/superagent/-/superagent-7.1.1.tgz",
+      "integrity": "sha512-CQ2weSS6M+doIwwYFoMatklhRbx6sVNdB99OEJ5czcP3cng76Ljqus694knFWgOj3RkrtxZqIgpe6vhe0J7QWQ==",
       "dev": true,
       "dependencies": {
         "component-emitter": "^1.3.0",
-        "cookiejar": "^2.1.2",
-        "debug": "^4.1.1",
-        "fast-safe-stringify": "^2.0.7",
-        "form-data": "^3.0.0",
-        "formidable": "^1.2.2",
+        "cookiejar": "^2.1.3",
+        "debug": "^4.3.3",
+        "fast-safe-stringify": "^2.1.1",
+        "form-data": "^4.0.0",
+        "formidable": "^2.0.1",
         "methods": "^1.1.2",
-        "mime": "^2.4.6",
-        "qs": "^6.9.4",
+        "mime": "^2.5.0",
+        "qs": "^6.10.1",
         "readable-stream": "^3.6.0",
-        "semver": "^7.3.2"
+        "semver": "^7.3.5"
       },
       "engines": {
-        "node": ">= 7.0.0"
+        "node": ">=6.4.0 <13 || >=14"
+      }
+    },
+    "node_modules/superagent/node_modules/debug": {
+      "version": "4.3.3",
+      "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
+      "integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
+      "dev": true,
+      "dependencies": {
+        "ms": "2.1.2"
+      },
+      "engines": {
+        "node": ">=6.0"
+      },
+      "peerDependenciesMeta": {
+        "supports-color": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/superagent/node_modules/form-data": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz",
+      "integrity": "sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==",
+      "dev": true,
+      "dependencies": {
+        "asynckit": "^0.4.0",
+        "combined-stream": "^1.0.8",
+        "mime-types": "^2.1.12"
+      },
+      "engines": {
+        "node": ">= 6"
       }
     },
     "node_modules/superagent/node_modules/qs": {
-      "version": "6.10.1",
-      "resolved": "https://registry.npmjs.org/qs/-/qs-6.10.1.tgz",
-      "integrity": "sha512-M528Hph6wsSVOBiYUnGf+K/7w0hNshs/duGsNXPUCLH5XAqjEtiPGwNONLV0tBH8NoGb0mvD5JubnUTrujKDTg==",
+      "version": "6.10.3",
+      "resolved": "https://registry.npmjs.org/qs/-/qs-6.10.3.tgz",
+      "integrity": "sha512-wr7M2E0OFRfIfJZjKGieI8lBKb7fRCH4Fv5KNPEs7gJ8jadvotdsS08PzOKR7opXhZ/Xkjtt3WF9g38drmyRqQ==",
       "dev": true,
       "dependencies": {
         "side-channel": "^1.0.4"
@@ -20788,13 +20504,13 @@
       }
     },
     "node_modules/supertest": {
-      "version": "6.1.6",
-      "resolved": "https://registry.npmjs.org/supertest/-/supertest-6.1.6.tgz",
-      "integrity": "sha512-0hACYGNJ8OHRg8CRITeZOdbjur7NLuNs0mBjVhdpxi7hP6t3QIbOzLON5RTUmZcy2I9riuII3+Pr2C7yztrIIg==",
+      "version": "6.2.2",
+      "resolved": "https://registry.npmjs.org/supertest/-/supertest-6.2.2.tgz",
+      "integrity": "sha512-wCw9WhAtKJsBvh07RaS+/By91NNE0Wh0DN19/hWPlBOU8tAfOtbZoVSV4xXeoKoxgPx0rx2y+y+8660XtE7jzg==",
       "dev": true,
       "dependencies": {
         "methods": "^1.1.2",
-        "superagent": "^6.1.0"
+        "superagent": "^7.1.0"
       },
       "engines": {
         "node": ">=6.0.0"
@@ -21098,17 +20814,6 @@
       "integrity": "sha512-8hmiGIJMDlwjg7dlJ4yKGLK8EsYqKgPWbG3b4wjJddKNwc7N7Dpn08Df4szr/sZdMVeOstrdYSsqzX6BYbcB+w==",
       "dev": true
     },
-    "node_modules/throng": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/throng/-/throng-5.0.0.tgz",
-      "integrity": "sha512-nrq7+qQhn/DL8yW/wiwImTepfi6ynOCAe7moSwgoYN1F32yQMdBkuFII40oAkb3cDfaL6q5BIoFTDCHdMWQ8Pw==",
-      "dependencies": {
-        "lodash": "^4.17.20"
-      },
-      "engines": {
-        "node": ">= 10"
-      }
-    },
     "node_modules/through": {
       "version": "2.3.8",
       "resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
@@ -21394,7 +21099,7 @@
       "version": "0.6.0",
       "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz",
       "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=",
-      "devOptional": true,
+      "dev": true,
       "dependencies": {
         "safe-buffer": "^5.0.1"
       },
@@ -21402,12 +21107,6 @@
         "node": "*"
       }
     },
-    "node_modules/tweetnacl": {
-      "version": "0.14.5",
-      "resolved": "https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz",
-      "integrity": "sha1-WuaBd/GS1EViadEIr6k/+HQ/T2Q=",
-      "optional": true
-    },
     "node_modules/type-check": {
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
@@ -21778,7 +21477,7 @@
       "version": "0.1.2",
       "resolved": "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz",
       "integrity": "sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==",
-      "devOptional": true,
+      "dev": true,
       "engines": {
         "node": ">= 4.0.0"
       }
@@ -22048,20 +21747,6 @@
         "node": ">= 0.8"
       }
     },
-    "node_modules/verror": {
-      "version": "1.10.0",
-      "resolved": "https://registry.npmjs.org/verror/-/verror-1.10.0.tgz",
-      "integrity": "sha1-OhBcoXBTr1XW4nDB+CiGguGNpAA=",
-      "engines": [
-        "node >=0.6.0"
-      ],
-      "optional": true,
-      "dependencies": {
-        "assert-plus": "^1.0.0",
-        "core-util-is": "1.0.2",
-        "extsprintf": "^1.2.0"
-      }
-    },
     "node_modules/vfile": {
       "version": "5.1.1",
       "resolved": "https://registry.npmjs.org/vfile/-/vfile-5.1.1.tgz",
@@ -22440,144 +22125,130 @@
       }
     },
     "node_modules/website-scraper": {
-      "version": "4.2.3",
-      "resolved": "https://registry.npmjs.org/website-scraper/-/website-scraper-4.2.3.tgz",
-      "integrity": "sha512-Pqrirzwt02NtaTFkBulF3fGSvPGOAVpdwPFHzoh49gFjU2GgaEgoW8WMlhPbzRcQkd6+XmsU+LZeW9SiluDHkA==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/website-scraper/-/website-scraper-5.0.0.tgz",
+      "integrity": "sha512-wZP7fSQR86UZSCXfKzd5OlgBb6AdxXN6gVN07Hy2wYxp2+GeqQAIw+sbqXNlPQnpJLwmRZDWp2u6KeuaFOhotw==",
       "optional": true,
       "dependencies": {
-        "bluebird": "^3.0.1",
-        "cheerio": "0.22.0",
+        "cheerio": "1.0.0-rc.10",
         "css-url-parser": "^1.0.0",
-        "debug": "^4.0.1",
-        "fs-extra": "^8.0.1",
-        "he": "^1.1.0",
-        "lodash": "^4.17.20",
-        "normalize-url": "^4.0.0",
-        "p-queue": "^6.6.1",
-        "request": "^2.85.0",
+        "debug": "^4.3.1",
+        "fs-extra": "^10.0.0",
+        "got": "^12.0.0",
+        "lodash": "^4.17.21",
+        "normalize-url": "^7.0.2",
+        "p-queue": "^7.1.0",
         "sanitize-filename": "^1.6.3",
-        "srcset": "^2.0.0"
-      }
-    },
-    "node_modules/website-scraper/node_modules/cheerio": {
-      "version": "0.22.0",
-      "resolved": "https://registry.npmjs.org/cheerio/-/cheerio-0.22.0.tgz",
-      "integrity": "sha1-qbqoYKP5tZWmuBsahocxIe06Jp4=",
-      "optional": true,
-      "dependencies": {
-        "css-select": "~1.2.0",
-        "dom-serializer": "~0.1.0",
-        "entities": "~1.1.1",
-        "htmlparser2": "^3.9.1",
-        "lodash.assignin": "^4.0.9",
-        "lodash.bind": "^4.1.4",
-        "lodash.defaults": "^4.0.1",
-        "lodash.filter": "^4.4.0",
-        "lodash.flatten": "^4.2.0",
-        "lodash.foreach": "^4.3.0",
-        "lodash.map": "^4.4.0",
-        "lodash.merge": "^4.4.0",
-        "lodash.pick": "^4.2.1",
-        "lodash.reduce": "^4.4.0",
-        "lodash.reject": "^4.4.0",
-        "lodash.some": "^4.4.0"
+        "srcset": "^5.0.0"
       },
       "engines": {
-        "node": ">= 0.6"
+        "node": ">=14.14"
       }
     },
-    "node_modules/website-scraper/node_modules/css-select": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/css-select/-/css-select-1.2.0.tgz",
-      "integrity": "sha1-KzoRBTnFNV8c2NMUYj6HCxIeyFg=",
+    "node_modules/website-scraper/node_modules/@szmarczak/http-timer": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/@szmarczak/http-timer/-/http-timer-5.0.1.tgz",
+      "integrity": "sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw==",
       "optional": true,
       "dependencies": {
-        "boolbase": "~1.0.0",
-        "css-what": "2.1",
-        "domutils": "1.5.1",
-        "nth-check": "~1.0.1"
+        "defer-to-connect": "^2.0.1"
+      },
+      "engines": {
+        "node": ">=14.16"
       }
     },
-    "node_modules/website-scraper/node_modules/css-what": {
-      "version": "2.1.3",
-      "resolved": "https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz",
-      "integrity": "sha512-a+EPoD+uZiNfh+5fxw2nO9QwFa6nJe2Or35fGY6Ipw1R3R4AGz1d1TEZrCegvw2YTmZ0jXirGYlzxxpYSHwpEg==",
+    "node_modules/website-scraper/node_modules/cacheable-lookup": {
+      "version": "6.0.4",
+      "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-6.0.4.tgz",
+      "integrity": "sha512-mbcDEZCkv2CZF4G01kr8eBd/5agkt9oCqz75tJMSIsquvRZ2sL6Hi5zGVKi/0OSC9oO1GHfJ2AV0ZIOY9vye0A==",
       "optional": true,
       "engines": {
-        "node": "*"
+        "node": ">=10.6.0"
       }
     },
-    "node_modules/website-scraper/node_modules/dom-serializer": {
-      "version": "0.1.1",
-      "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-0.1.1.tgz",
-      "integrity": "sha512-l0IU0pPzLWSHBcieZbpOKgkIn3ts3vAh7ZuFyXNwJxJXk/c4Gwj9xaTJwIDVQCXawWD0qb3IzMGH5rglQaO0XA==",
+    "node_modules/website-scraper/node_modules/get-stream": {
+      "version": "6.0.1",
+      "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz",
+      "integrity": "sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==",
       "optional": true,
-      "dependencies": {
-        "domelementtype": "^1.3.0",
-        "entities": "^1.1.1"
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/website-scraper/node_modules/domelementtype": {
-      "version": "1.3.1",
-      "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-1.3.1.tgz",
-      "integrity": "sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==",
-      "optional": true
-    },
-    "node_modules/website-scraper/node_modules/domhandler": {
-      "version": "2.4.2",
-      "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-2.4.2.tgz",
-      "integrity": "sha512-JiK04h0Ht5u/80fdLMCEmV4zkNh2BcoMFBmZ/91WtYZ8qVXSKjiw7fXMgFPnHcSZgOo3XdinHvmnDUeMf5R4wA==",
+    "node_modules/website-scraper/node_modules/got": {
+      "version": "12.0.1",
+      "resolved": "https://registry.npmjs.org/got/-/got-12.0.1.tgz",
+      "integrity": "sha512-1Zhoh+lDej3t7Ks1BP/Jufn+rNqdiHQgUOcTxHzg2Dao1LQfp5S4Iq0T3iBxN4Zdo7QqCJL+WJUNzDX6rCP2Ew==",
       "optional": true,
       "dependencies": {
-        "domelementtype": "1"
+        "@sindresorhus/is": "^4.2.0",
+        "@szmarczak/http-timer": "^5.0.1",
+        "@types/cacheable-request": "^6.0.2",
+        "@types/responselike": "^1.0.0",
+        "cacheable-lookup": "^6.0.4",
+        "cacheable-request": "^7.0.2",
+        "decompress-response": "^6.0.0",
+        "form-data-encoder": "1.7.1",
+        "get-stream": "^6.0.1",
+        "http2-wrapper": "^2.1.9",
+        "lowercase-keys": "^3.0.0",
+        "p-cancelable": "^3.0.0",
+        "responselike": "^2.0.0"
+      },
+      "engines": {
+        "node": ">=14.16"
+      },
+      "funding": {
+        "url": "https://github.com/sindresorhus/got?sponsor=1"
       }
     },
-    "node_modules/website-scraper/node_modules/domutils": {
-      "version": "1.5.1",
-      "resolved": "https://registry.npmjs.org/domutils/-/domutils-1.5.1.tgz",
-      "integrity": "sha1-3NhIiib1Y9YQeeSMn3t+Mjc2gs8=",
+    "node_modules/website-scraper/node_modules/http2-wrapper": {
+      "version": "2.1.10",
+      "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.10.tgz",
+      "integrity": "sha512-QHgsdYkieKp+6JbXP25P+tepqiHYd+FVnDwXpxi/BlUcoIB0nsmTOymTNvETuTO+pDuwcSklPE72VR3DqV+Haw==",
       "optional": true,
       "dependencies": {
-        "dom-serializer": "0",
-        "domelementtype": "1"
+        "quick-lru": "^5.1.1",
+        "resolve-alpn": "^1.2.0"
+      },
+      "engines": {
+        "node": ">=10.19.0"
       }
     },
-    "node_modules/website-scraper/node_modules/entities": {
-      "version": "1.1.2",
-      "resolved": "https://registry.npmjs.org/entities/-/entities-1.1.2.tgz",
-      "integrity": "sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==",
-      "optional": true
-    },
-    "node_modules/website-scraper/node_modules/htmlparser2": {
-      "version": "3.10.1",
-      "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-3.10.1.tgz",
-      "integrity": "sha512-IgieNijUMbkDovyoKObU1DUhm1iwNYE/fuifEoEHfd1oZKZDaONBSkal7Y01shxsM49R4XaMdGez3WnF9UfiCQ==",
+    "node_modules/website-scraper/node_modules/lowercase-keys": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-3.0.0.tgz",
+      "integrity": "sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ==",
       "optional": true,
-      "dependencies": {
-        "domelementtype": "^1.3.1",
-        "domhandler": "^2.3.0",
-        "domutils": "^1.5.1",
-        "entities": "^1.1.1",
-        "inherits": "^2.0.1",
-        "readable-stream": "^3.1.1"
+      "engines": {
+        "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/website-scraper/node_modules/normalize-url": {
-      "version": "4.5.1",
-      "resolved": "https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.1.tgz",
-      "integrity": "sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==",
+      "version": "7.0.3",
+      "resolved": "https://registry.npmjs.org/normalize-url/-/normalize-url-7.0.3.tgz",
+      "integrity": "sha512-RiCOdwdPnzvwcBFJE4iI1ss3dMVRIrEzFpn8ftje6iBfzBInqlnRrNhxcLwBEKjPPXQKzm1Ptlxtaiv9wdcj5w==",
       "optional": true,
       "engines": {
-        "node": ">=8"
+        "node": ">=12.20"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/website-scraper/node_modules/nth-check": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz",
-      "integrity": "sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==",
+    "node_modules/website-scraper/node_modules/p-cancelable": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/p-cancelable/-/p-cancelable-3.0.0.tgz",
+      "integrity": "sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==",
       "optional": true,
-      "dependencies": {
-        "boolbase": "~1.0.0"
+      "engines": {
+        "node": ">=12.20"
       }
     },
     "node_modules/whatwg-encoding": {
@@ -22897,12 +22568,6 @@
         "fd-slicer": "~1.1.0"
       }
     },
-    "node_modules/yesno": {
-      "version": "0.3.1",
-      "resolved": "https://registry.npmjs.org/yesno/-/yesno-0.3.1.tgz",
-      "integrity": "sha512-7RbCXegyu6DykWPWU0YEtW8gFJH8KBL2d5l2fqB0XpkH0Y9rk59YSSWpzEv7yNJBGAouPc67h3kkq0CZkpBdFw==",
-      "dev": true
-    },
     "node_modules/yocto-queue": {
       "version": "0.1.0",
       "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
@@ -26570,14 +26235,11 @@
       "integrity": "sha1-iYUI2iIm84DfkEcoRWhJwVAaSw0=",
       "dev": true
     },
-    "asn1": {
-      "version": "0.2.6",
-      "resolved": "https://registry.npmjs.org/asn1/-/asn1-0.2.6.tgz",
-      "integrity": "sha512-ix/FxPn0MDjeyJ7i/yoHGFt/EX6LyNbxSEhPPXODPL+KB0VPk86UYfL0lMdy+KCnv+fmvIzySwaK5COwqVbWTQ==",
-      "optional": true,
-      "requires": {
-        "safer-buffer": "~2.1.0"
-      }
+    "asap": {
+      "version": "2.0.6",
+      "resolved": "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz",
+      "integrity": "sha1-5QNHYR1+aQlDIIu9r+vLwvuGbUY=",
+      "dev": true
     },
     "asn1.js": {
       "version": "5.4.1",
@@ -26608,12 +26270,6 @@
         "util": "^0.12.0"
       }
     },
-    "assert-plus": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/assert-plus/-/assert-plus-1.0.0.tgz",
-      "integrity": "sha1-8S4PPF13sLHN2RRpQuTpbB5N1SU=",
-      "optional": true
-    },
     "ast-types": {
       "version": "0.13.2",
       "resolved": "https://registry.npmjs.org/ast-types/-/ast-types-0.13.2.tgz",
@@ -26647,25 +26303,13 @@
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
       "integrity": "sha1-x57Zf380y48robyXkLzDZkdLS3k=",
-      "devOptional": true
+      "dev": true
     },
     "available-typed-arrays": {
       "version": "1.0.5",
       "resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.5.tgz",
       "integrity": "sha512-DMD0KiN46eipeziST1LPP/STfDU0sufISXmjSgvVsoU2tqxctQeASejWcfNtxYKqETM1UxQ8sp2OrSBWpHY6sw=="
     },
-    "aws-sign2": {
-      "version": "0.7.0",
-      "resolved": "https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.7.0.tgz",
-      "integrity": "sha1-tG6JCTSpWR8tL2+G1+ap8bP+dqg=",
-      "optional": true
-    },
-    "aws4": {
-      "version": "1.11.0",
-      "resolved": "https://registry.npmjs.org/aws4/-/aws4-1.11.0.tgz",
-      "integrity": "sha512-xh1Rl34h6Fi1DC2WWKfxUTVqRsNnr6LsKz2+hfwDxQJWmrx8+c7ylaqBMcHfl1U1r2dsifOvKX3LQuLNZ+XSvA==",
-      "optional": true
-    },
     "axe-core": {
       "version": "4.3.5",
       "resolved": "https://registry.npmjs.org/axe-core/-/axe-core-4.3.5.tgz",
@@ -26997,13 +26641,13 @@
       }
     },
     "babel-plugin-polyfill-corejs3": {
-      "version": "0.5.2",
-      "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.2.tgz",
-      "integrity": "sha512-G3uJih0XWiID451fpeFaYGVuxHEjzKTHtc9uGFEjR6hHrvNzeS/PX+LLLcetJcytsB5m4j+K3o/EpXJNb/5IEQ==",
+      "version": "0.5.1",
+      "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.5.1.tgz",
+      "integrity": "sha512-TihqEe4sQcb/QcPJvxe94/9RZuLQuF1+To4WqQcRvc+3J3gLCPIPgDKzGLG6zmQLfH3nn25heRuDNkS2KR4I8A==",
       "dev": true,
       "requires": {
         "@babel/helper-define-polyfill-provider": "^0.3.1",
-        "core-js-compat": "^3.21.0"
+        "core-js-compat": "^3.20.0"
       }
     },
     "babel-plugin-polyfill-regenerator": {
@@ -27582,15 +27226,6 @@
       "resolved": "https://registry.npmjs.org/bcp-47-match/-/bcp-47-match-2.0.0.tgz",
       "integrity": "sha512-B3/f3fqIdWLUQE/iFIahFmDKB6X2U7RcugRcdEj2Ntju13zrewCSqnEwG92iUUKfkZ6I+UMtT2NCBwLCvXBOmg=="
     },
-    "bcrypt-pbkdf": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.2.tgz",
-      "integrity": "sha1-pDAdOJtqQ/m2f/PKEaP2Y342Dp4=",
-      "optional": true,
-      "requires": {
-        "tweetnacl": "^0.14.3"
-      }
-    },
     "before-after-hook": {
       "version": "2.2.2",
       "resolved": "https://registry.npmjs.org/before-after-hook/-/before-after-hook-2.2.2.tgz",
@@ -27633,7 +27268,7 @@
       "version": "3.7.2",
       "resolved": "https://registry.npmjs.org/bluebird/-/bluebird-3.7.2.tgz",
       "integrity": "sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==",
-      "devOptional": true
+      "dev": true
     },
     "bmp-js": {
       "version": "0.1.0",
@@ -27990,12 +27625,6 @@
           "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==",
           "dev": true
         },
-        "quick-lru": {
-          "version": "5.1.1",
-          "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
-          "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
-          "dev": true
-        },
         "type-fest": {
           "version": "1.4.0",
           "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
@@ -28025,12 +27654,6 @@
         "upper-case-first": "^2.0.2"
       }
     },
-    "caseless": {
-      "version": "0.12.0",
-      "resolved": "https://registry.npmjs.org/caseless/-/caseless-0.12.0.tgz",
-      "integrity": "sha1-G2gcIf+EAzyCZUMJBolCDRhxUdw=",
-      "optional": true
-    },
     "ccount": {
       "version": "2.0.0",
       "resolved": "https://registry.npmjs.org/ccount/-/ccount-2.0.0.tgz",
@@ -28359,7 +27982,7 @@
       "version": "1.0.8",
       "resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.8.tgz",
       "integrity": "sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==",
-      "devOptional": true,
+      "dev": true,
       "requires": {
         "delayed-stream": "~1.0.0"
       }
@@ -28591,9 +28214,9 @@
       "dev": true
     },
     "core-js-compat": {
-      "version": "3.21.0",
-      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.21.0.tgz",
-      "integrity": "sha512-OSXseNPSK2OPJa6GdtkMz/XxeXx8/CJvfhQWTqd6neuUraujcL4jVsjkLQz1OWnax8xVQJnRPe0V2jqNWORA+A==",
+      "version": "3.20.2",
+      "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.20.2.tgz",
+      "integrity": "sha512-qZEzVQ+5Qh6cROaTPFLNS4lkvQ6mBzE3R6A6EEpssj7Zr2egMHgsy4XapdifqJDGC9CBiNv7s+ejI96rLNQFdg==",
       "dev": true,
       "requires": {
         "browserslist": "^4.19.1",
@@ -28848,15 +28471,6 @@
       "integrity": "sha512-VvdQIPGdWP0SqFXghj79Wf/5LArmreyMsGLa6FG6iC4t3j7j5s71TrwWmT/4akbDQIqjfACkLZmjXhA7g2oUZw==",
       "dev": true
     },
-    "dashdash": {
-      "version": "1.14.1",
-      "resolved": "https://registry.npmjs.org/dashdash/-/dashdash-1.14.1.tgz",
-      "integrity": "sha1-hTz6D3y+L+1d4gMmuN1YEDX24vA=",
-      "optional": true,
-      "requires": {
-        "assert-plus": "^1.0.0"
-      }
-    },
     "data-uri-to-buffer": {
       "version": "3.0.1",
       "resolved": "https://registry.npmjs.org/data-uri-to-buffer/-/data-uri-to-buffer-3.0.1.tgz",
@@ -28986,7 +28600,7 @@
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
       "integrity": "sha1-3zrhmayt+31ECqrgsp4icrJOxhk=",
-      "devOptional": true
+      "dev": true
     },
     "denque": {
       "version": "1.5.1",
@@ -29041,6 +28655,16 @@
       "integrity": "sha512-VvlVYY+VDJe639yHs5PHISzdWTLL3Aw8rO4cvUtwvoxFd6FHbE4OpHHcde52M6096uYYazAmd4l0o5VuFRO2WA==",
       "optional": true
     },
+    "dezalgo": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/dezalgo/-/dezalgo-1.0.3.tgz",
+      "integrity": "sha1-f3Qt4Gb8dIvI24IFad3c5Jvw1FY=",
+      "dev": true,
+      "requires": {
+        "asap": "^2.0.0",
+        "wrappy": "1"
+      }
+    },
     "diff": {
       "version": "5.0.0",
       "resolved": "https://registry.npmjs.org/diff/-/diff-5.0.0.tgz",
@@ -29270,16 +28894,6 @@
       "integrity": "sha1-7gHdHKwO08vH/b6jfcCo8c4ALOI=",
       "dev": true
     },
-    "ecc-jsbn": {
-      "version": "0.1.2",
-      "resolved": "https://registry.npmjs.org/ecc-jsbn/-/ecc-jsbn-0.1.2.tgz",
-      "integrity": "sha1-OoOpBOVDUyh4dMVkt1SThoSamMk=",
-      "optional": true,
-      "requires": {
-        "jsbn": "~0.1.0",
-        "safer-buffer": "^2.1.0"
-      }
-    },
     "ee-first": {
       "version": "1.1.1",
       "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz",
@@ -30184,12 +29798,6 @@
         "yauzl": "^2.10.0"
       }
     },
-    "extsprintf": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/extsprintf/-/extsprintf-1.3.0.tgz",
-      "integrity": "sha1-lpGEQOMEGnpBT4xS48V06zw+HgU=",
-      "optional": true
-    },
     "fast-deep-equal": {
       "version": "3.1.3",
       "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
@@ -30448,12 +30056,6 @@
       "resolved": "https://registry.npmjs.org/foreach/-/foreach-2.0.5.tgz",
       "integrity": "sha1-C+4AUBiusmDQo6865ljdATbsG5k="
     },
-    "forever-agent": {
-      "version": "0.6.1",
-      "resolved": "https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz",
-      "integrity": "sha1-+8cfDEGt6zf5bFd60e1C2P2sypE=",
-      "optional": true
-    },
     "form-data": {
       "version": "3.0.1",
       "resolved": "https://registry.npmjs.org/form-data/-/form-data-3.0.1.tgz",
@@ -30465,6 +30067,12 @@
         "mime-types": "^2.1.12"
       }
     },
+    "form-data-encoder": {
+      "version": "1.7.1",
+      "resolved": "https://registry.npmjs.org/form-data-encoder/-/form-data-encoder-1.7.1.tgz",
+      "integrity": "sha512-EFRDrsMm/kyqbTQocNvRXMLjc7Es2Vk+IQFx/YW7hkUH1eBl4J1fqiP34l74Yt0pFLCNpc06fkbVk00008mzjg==",
+      "optional": true
+    },
     "format": {
       "version": "0.2.2",
       "resolved": "https://registry.npmjs.org/format/-/format-0.2.2.tgz",
@@ -30479,10 +30087,24 @@
       }
     },
     "formidable": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/formidable/-/formidable-1.2.2.tgz",
-      "integrity": "sha512-V8gLm+41I/8kguQ4/o1D3RIHRmhYFG4pnNyonvua+40rqcEmT4+V71yaZ3B457xbbgCsCfjSPi65u/W6vK1U5Q==",
-      "dev": true
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/formidable/-/formidable-2.0.1.tgz",
+      "integrity": "sha512-rjTMNbp2BpfQShhFbR3Ruk3qk2y9jKpvMW78nJgx8QKtxjDVrwbZG+wvDOmVbifHyOUOQJXxqEy6r0faRrPzTQ==",
+      "dev": true,
+      "requires": {
+        "dezalgo": "1.0.3",
+        "hexoid": "1.0.0",
+        "once": "1.4.0",
+        "qs": "6.9.3"
+      },
+      "dependencies": {
+        "qs": {
+          "version": "6.9.3",
+          "resolved": "https://registry.npmjs.org/qs/-/qs-6.9.3.tgz",
+          "integrity": "sha512-EbZYNarm6138UKKq46tdx08Yo/q9ZhFoAXAI1meAFd2GtbRDhbZY2WQSICskT0c5q99aFzLG1D4nvTk9tqfXIw==",
+          "dev": true
+        }
+      }
     },
     "forwarded": {
       "version": "0.2.0",
@@ -30513,14 +30135,22 @@
       "optional": true
     },
     "fs-extra": {
-      "version": "8.1.0",
-      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-8.1.0.tgz",
-      "integrity": "sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==",
+      "version": "10.0.0",
+      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-10.0.0.tgz",
+      "integrity": "sha512-C5owb14u9eJwizKGdchcDUQeFtlSHHthBk8pbX9Vc1PFZrLombudjDnNns88aYslCyF6IY5SUw3Roz6xShcEIQ==",
       "optional": true,
       "requires": {
         "graceful-fs": "^4.2.0",
-        "jsonfile": "^4.0.0",
-        "universalify": "^0.1.0"
+        "jsonfile": "^6.0.1",
+        "universalify": "^2.0.0"
+      },
+      "dependencies": {
+        "universalify": {
+          "version": "2.0.0",
+          "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
+          "integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==",
+          "optional": true
+        }
       }
     },
     "fs.realpath": {
@@ -30643,15 +30273,6 @@
         "get-intrinsic": "^1.1.1"
       }
     },
-    "getpass": {
-      "version": "0.1.7",
-      "resolved": "https://registry.npmjs.org/getpass/-/getpass-0.1.7.tgz",
-      "integrity": "sha1-Xv+OPmhNVprkyysSgmBOi6YhSfo=",
-      "optional": true,
-      "requires": {
-        "assert-plus": "^1.0.0"
-      }
-    },
     "gifwrap": {
       "version": "0.9.2",
       "resolved": "https://registry.npmjs.org/gifwrap/-/gifwrap-0.9.2.tgz",
@@ -30917,42 +30538,6 @@
         }
       }
     },
-    "har-schema": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/har-schema/-/har-schema-2.0.0.tgz",
-      "integrity": "sha1-qUwiJOvKwEeCoNkDVSHyRzW37JI=",
-      "optional": true
-    },
-    "har-validator": {
-      "version": "5.1.5",
-      "resolved": "https://registry.npmjs.org/har-validator/-/har-validator-5.1.5.tgz",
-      "integrity": "sha512-nmT2T0lljbxdQZfspsno9hgrG3Uir6Ks5afism62poxqBM6sDnMEuPmzTq8XN0OEwqKLLdh1jQI3qyE66Nzb3w==",
-      "optional": true,
-      "requires": {
-        "ajv": "^6.12.3",
-        "har-schema": "^2.0.0"
-      },
-      "dependencies": {
-        "ajv": {
-          "version": "6.12.6",
-          "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
-          "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
-          "optional": true,
-          "requires": {
-            "fast-deep-equal": "^3.1.1",
-            "fast-json-stable-stringify": "^2.0.0",
-            "json-schema-traverse": "^0.4.1",
-            "uri-js": "^4.2.2"
-          }
-        },
-        "json-schema-traverse": {
-          "version": "0.4.1",
-          "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
-          "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
-          "optional": true
-        }
-      }
-    },
     "hard-rejection": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/hard-rejection/-/hard-rejection-2.1.0.tgz",
@@ -31234,6 +30819,12 @@
         "tunnel-agent": "^0.6.0"
       }
     },
+    "hexoid": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/hexoid/-/hexoid-1.0.0.tgz",
+      "integrity": "sha512-QFLV0taWQOZtvIRIAdBChesmogZrtuXvVWsFHZTk2SU+anspqZ2vMnoLg7IE1+Uk16N19APic1BuF8bC8c2m5g==",
+      "dev": true
+    },
     "highlight.js": {
       "version": "11.2.0",
       "resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-11.2.0.tgz",
@@ -31371,17 +30962,6 @@
         "debug": "4"
       }
     },
-    "http-signature": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/http-signature/-/http-signature-1.2.0.tgz",
-      "integrity": "sha1-muzZJRFHcvPZW2WmCruPfBj7rOE=",
-      "optional": true,
-      "requires": {
-        "assert-plus": "^1.0.0",
-        "jsprim": "^1.2.2",
-        "sshpk": "^1.7.0"
-      }
-    },
     "http-status-code": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/http-status-code/-/http-status-code-2.1.0.tgz",
@@ -31406,13 +30986,6 @@
       "requires": {
         "quick-lru": "^5.1.1",
         "resolve-alpn": "^1.0.0"
-      },
-      "dependencies": {
-        "quick-lru": {
-          "version": "5.1.1",
-          "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
-          "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA=="
-        }
       }
     },
     "https-browserify": {
@@ -31874,7 +31447,7 @@
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/is-typedarray/-/is-typedarray-1.0.0.tgz",
       "integrity": "sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=",
-      "devOptional": true
+      "dev": true
     },
     "is-url": {
       "version": "1.2.4",
@@ -31938,12 +31511,6 @@
       "integrity": "sha1-TkMekrEalzFjaqH5yNHMvP2reN8=",
       "optional": true
     },
-    "isstream": {
-      "version": "0.1.2",
-      "resolved": "https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz",
-      "integrity": "sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=",
-      "optional": true
-    },
     "istanbul-lib-coverage": {
       "version": "3.2.0",
       "resolved": "https://registry.npmjs.org/istanbul-lib-coverage/-/istanbul-lib-coverage-3.2.0.tgz",
@@ -32836,12 +32403,6 @@
         "argparse": "^2.0.1"
       }
     },
-    "jsbn": {
-      "version": "0.1.1",
-      "resolved": "https://registry.npmjs.org/jsbn/-/jsbn-0.1.1.tgz",
-      "integrity": "sha1-peZUwuWi3rXyAdls77yoDA7y9RM=",
-      "optional": true
-    },
     "jsdom": {
       "version": "16.7.0",
       "resolved": "https://registry.npmjs.org/jsdom/-/jsdom-16.7.0.tgz",
@@ -32908,12 +32469,6 @@
       "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==",
       "dev": true
     },
-    "json-schema": {
-      "version": "0.4.0",
-      "resolved": "https://registry.npmjs.org/json-schema/-/json-schema-0.4.0.tgz",
-      "integrity": "sha512-es94M3nTIfsEPisRafak+HDLfHXnKBhV3vU5eqPcS3flIWqcxJWgXHXiey3YrpaNsanY5ei1VoYEbOzijuq9BA==",
-      "optional": true
-    },
     "json-schema-traverse": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
@@ -32929,7 +32484,7 @@
       "version": "5.0.1",
       "resolved": "https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz",
       "integrity": "sha1-Epai1Y/UXxmg9s4B1lcB4sc1tus=",
-      "devOptional": true
+      "dev": true
     },
     "json5": {
       "version": "2.2.0",
@@ -32946,24 +32501,21 @@
       "dev": true
     },
     "jsonfile": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-4.0.0.tgz",
-      "integrity": "sha1-h3Gq4HmbZAdrdmQPygWPnBDjPss=",
+      "version": "6.1.0",
+      "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
+      "integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
       "optional": true,
       "requires": {
-        "graceful-fs": "^4.1.6"
-      }
-    },
-    "jsprim": {
-      "version": "1.4.2",
-      "resolved": "https://registry.npmjs.org/jsprim/-/jsprim-1.4.2.tgz",
-      "integrity": "sha512-P2bSOMAc/ciLz6DzgjVlGJP9+BrJWu5UDGK70C2iweC5QBIeFf0ZXRvGjEj2uYgrY2MkAAhsSWHDWlFtEroZWw==",
-      "optional": true,
-      "requires": {
-        "assert-plus": "1.0.0",
-        "extsprintf": "1.3.0",
-        "json-schema": "0.4.0",
-        "verror": "1.10.0"
+        "graceful-fs": "^4.1.6",
+        "universalify": "^2.0.0"
+      },
+      "dependencies": {
+        "universalify": {
+          "version": "2.0.0",
+          "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.0.tgz",
+          "integrity": "sha512-hAZsKq7Yy11Zu1DE0OzWjw7nnLZmJZYTDZZyEFHZdUhV8FkH5MCfoU1XMaxXovpyW5nq5scPqq0ZDP9Zyl04oQ==",
+          "optional": true
+        }
       }
     },
     "jsx-ast-utils": {
@@ -33332,18 +32884,6 @@
       "resolved": "https://registry.npmjs.org/lodash-es/-/lodash-es-4.17.21.tgz",
       "integrity": "sha512-mKnC+QJ9pWVzv+C4/U3rRsHapFfHvQFoFB92e52xeyGMcX6/OlIl78je1u8vePzYZSkkogMPJ2yjxxsb89cxyw=="
     },
-    "lodash.assignin": {
-      "version": "4.2.0",
-      "resolved": "https://registry.npmjs.org/lodash.assignin/-/lodash.assignin-4.2.0.tgz",
-      "integrity": "sha1-uo31+4QesKPoBEIysOJjqNxqKKI=",
-      "optional": true
-    },
-    "lodash.bind": {
-      "version": "4.2.1",
-      "resolved": "https://registry.npmjs.org/lodash.bind/-/lodash.bind-4.2.1.tgz",
-      "integrity": "sha1-euMBfpOWIqwxt9fX3LGzTbFpDTU=",
-      "optional": true
-    },
     "lodash.clonedeep": {
       "version": "4.5.0",
       "resolved": "https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz",
@@ -33356,59 +32896,11 @@
       "integrity": "sha1-gteb/zCmfEAF/9XiUVMArZyk168=",
       "dev": true
     },
-    "lodash.defaults": {
-      "version": "4.2.0",
-      "resolved": "https://registry.npmjs.org/lodash.defaults/-/lodash.defaults-4.2.0.tgz",
-      "integrity": "sha1-0JF4cW/+pN3p5ft7N/bwgCJ0WAw=",
-      "optional": true
-    },
-    "lodash.filter": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.filter/-/lodash.filter-4.6.0.tgz",
-      "integrity": "sha1-ZosdSYFgOuHMWm+nYBQ+SAtMSs4=",
-      "optional": true
-    },
-    "lodash.flatten": {
-      "version": "4.4.0",
-      "resolved": "https://registry.npmjs.org/lodash.flatten/-/lodash.flatten-4.4.0.tgz",
-      "integrity": "sha1-8xwiIlqWMtK7+OSt2+8kCqdlph8=",
-      "optional": true
-    },
-    "lodash.foreach": {
-      "version": "4.5.0",
-      "resolved": "https://registry.npmjs.org/lodash.foreach/-/lodash.foreach-4.5.0.tgz",
-      "integrity": "sha1-Gmo16s5AEoDH8G3d7DUWWrJ+PlM=",
-      "optional": true
-    },
-    "lodash.map": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.map/-/lodash.map-4.6.0.tgz",
-      "integrity": "sha1-dx7Hg540c9nEzeKLGTlMNWL09tM=",
-      "optional": true
-    },
     "lodash.merge": {
       "version": "4.6.2",
       "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
       "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
-      "devOptional": true
-    },
-    "lodash.pick": {
-      "version": "4.4.0",
-      "resolved": "https://registry.npmjs.org/lodash.pick/-/lodash.pick-4.4.0.tgz",
-      "integrity": "sha1-UvBWEP/53tQiYRRB7R/BI6AwAbM=",
-      "optional": true
-    },
-    "lodash.reduce": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.reduce/-/lodash.reduce-4.6.0.tgz",
-      "integrity": "sha1-8atrg5KZrUj3hKu/R2WW8DuRTTs=",
-      "optional": true
-    },
-    "lodash.reject": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.reject/-/lodash.reject-4.6.0.tgz",
-      "integrity": "sha1-gNZJLcFHCGS79YNTO2UfQqn1JBU=",
-      "optional": true
+      "dev": true
     },
     "lodash.set": {
       "version": "4.3.2",
@@ -33416,12 +32908,6 @@
       "integrity": "sha1-2HV7HagH3eJIFrDWqEvqGnYjCyM=",
       "dev": true
     },
-    "lodash.some": {
-      "version": "4.6.0",
-      "resolved": "https://registry.npmjs.org/lodash.some/-/lodash.some-4.6.0.tgz",
-      "integrity": "sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=",
-      "optional": true
-    },
     "lodash.sortby": {
       "version": "4.7.0",
       "resolved": "https://registry.npmjs.org/lodash.sortby/-/lodash.sortby-4.7.0.tgz",
@@ -35144,12 +34630,6 @@
       "integrity": "sha512-h2AatdwYH+JHiZpv7pt/gSX1XoRGb7L/qSIeuqA6GwYoF9w1vP1cw42TO0aI2pNyshRK5893hNSl+1//vHK7hQ==",
       "dev": true
     },
-    "oauth-sign": {
-      "version": "0.9.0",
-      "resolved": "https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.9.0.tgz",
-      "integrity": "sha512-fexhUFFPTGV8ybAtSIGbV6gOkSv8UtRbDBnAyLQw4QPKkgNlsH2ByPGtMUqdWkos6YCRmAqViwgZrJc/mRDzZQ==",
-      "optional": true
-    },
     "object-assign": {
       "version": "4.1.1",
       "resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
@@ -35332,23 +34812,20 @@
       }
     },
     "p-queue": {
-      "version": "6.6.2",
-      "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-6.6.2.tgz",
-      "integrity": "sha512-RwFpb72c/BhQLEXIZ5K2e+AhgNVmIejGlTgiB9MzZ0e93GRvqZ7uSi0dvRF7/XIXDeNkra2fNHBxTyPDGySpjQ==",
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-7.2.0.tgz",
+      "integrity": "sha512-Kvv7p13M46lTYLQ/PsZdaj/1Vj6u/8oiIJgyQyx4oVkOfHdd7M2EZvXigDvcsSzRwanCzQirV5bJPQFoSQt5MA==",
       "optional": true,
       "requires": {
-        "eventemitter3": "^4.0.4",
-        "p-timeout": "^3.2.0"
+        "eventemitter3": "^4.0.7",
+        "p-timeout": "^5.0.2"
       },
       "dependencies": {
         "p-timeout": {
-          "version": "3.2.0",
-          "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-3.2.0.tgz",
-          "integrity": "sha512-rhIwUycgwwKcP9yTOOFK/AKsAopjjCakVqLHePO3CC6Mir1Z99xT+R63jZxAT5lFZLa2inS5h+ZS2GvR99/FBg==",
-          "optional": true,
-          "requires": {
-            "p-finally": "^1.0.0"
-          }
+          "version": "5.0.2",
+          "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-5.0.2.tgz",
+          "integrity": "sha512-sEmji9Yaq+Tw+STwsGAE56hf7gMy9p0tQfJojIAamB7WHJYJKf1qlsg9jqBWG8q9VCxKPhZaP/AcXwEoBcYQhQ==",
+          "optional": true
         }
       }
     },
@@ -36196,12 +35673,6 @@
       "integrity": "sha1-elfrVQpng/kRUzH89GY9XI4AelA=",
       "optional": true
     },
-    "performance-now": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/performance-now/-/performance-now-2.1.0.tgz",
-      "integrity": "sha1-Ywn04OX6kT7BxpMHrjZLSzd8nns=",
-      "optional": true
-    },
     "phin": {
       "version": "2.9.3",
       "resolved": "https://registry.npmjs.org/phin/-/phin-2.9.3.tgz",
@@ -36499,7 +35970,7 @@
       "version": "1.8.0",
       "resolved": "https://registry.npmjs.org/psl/-/psl-1.8.0.tgz",
       "integrity": "sha512-RIdOzyoavK+hA18OGGWDqUTsCLhtA7IcZ/6NCs4fFJaHBDab+pDDmDIByWFRQJq2Cd7r1OoQxBGKOaztq+hjIQ==",
-      "devOptional": true
+      "dev": true
     },
     "pstree.remy": {
       "version": "1.1.8",
@@ -36632,6 +36103,11 @@
       "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
       "dev": true
     },
+    "quick-lru": {
+      "version": "5.1.1",
+      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
+      "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA=="
+    },
     "random-bytes": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/random-bytes/-/random-bytes-1.0.0.tgz",
@@ -37603,69 +37079,6 @@
         }
       }
     },
-    "request": {
-      "version": "2.88.2",
-      "resolved": "https://registry.npmjs.org/request/-/request-2.88.2.tgz",
-      "integrity": "sha512-MsvtOrfG9ZcrOwAW+Qi+F6HbD0CWXEh9ou77uOb7FM2WPhwT7smM833PzanhJLsgXjN89Ir6V2PczXNnMpwKhw==",
-      "optional": true,
-      "requires": {
-        "aws-sign2": "~0.7.0",
-        "aws4": "^1.8.0",
-        "caseless": "~0.12.0",
-        "combined-stream": "~1.0.6",
-        "extend": "~3.0.2",
-        "forever-agent": "~0.6.1",
-        "form-data": "~2.3.2",
-        "har-validator": "~5.1.3",
-        "http-signature": "~1.2.0",
-        "is-typedarray": "~1.0.0",
-        "isstream": "~0.1.2",
-        "json-stringify-safe": "~5.0.1",
-        "mime-types": "~2.1.19",
-        "oauth-sign": "~0.9.0",
-        "performance-now": "^2.1.0",
-        "qs": "~6.5.2",
-        "safe-buffer": "^5.1.2",
-        "tough-cookie": "~2.5.0",
-        "tunnel-agent": "^0.6.0",
-        "uuid": "^3.3.2"
-      },
-      "dependencies": {
-        "form-data": {
-          "version": "2.3.3",
-          "resolved": "https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz",
-          "integrity": "sha512-1lLKB2Mu3aGP1Q/2eCOx0fNbRMe7XdwktwOruhfqqd0rIJWwN4Dh+E3hrPSlDCXnSR7UtZ1N38rVXm+6+MEhJQ==",
-          "optional": true,
-          "requires": {
-            "asynckit": "^0.4.0",
-            "combined-stream": "^1.0.6",
-            "mime-types": "^2.1.12"
-          }
-        },
-        "qs": {
-          "version": "6.5.3",
-          "resolved": "https://registry.npmjs.org/qs/-/qs-6.5.3.tgz",
-          "integrity": "sha512-qxXIEh4pCGfHICj1mAJQ2/2XVZkjCDTcEgfoSQxc/fYivUZxTkk7L3bDBJSoNrEzXI17oUO5Dp07ktqE5KzczA==",
-          "optional": true
-        },
-        "tough-cookie": {
-          "version": "2.5.0",
-          "resolved": "https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.5.0.tgz",
-          "integrity": "sha512-nlLsUzgm1kfLXSXfRZMc1KLAugd4hqJHDTvc2hDIwS3mZAfMEuMbc03SujMF+GEcpaX/qboeycw6iO8JwVv2+g==",
-          "optional": true,
-          "requires": {
-            "psl": "^1.1.28",
-            "punycode": "^2.1.1"
-          }
-        },
-        "uuid": {
-          "version": "3.4.0",
-          "resolved": "https://registry.npmjs.org/uuid/-/uuid-3.4.0.tgz",
-          "integrity": "sha512-HjSDRw6gZE5JMggctHBcjVak08+KEVhSIiDzFnT9S9aegmp85S/bReBVTb4QTFaRNptJ9kuYaNhnbNEOkbKb/A==",
-          "optional": true
-        }
-      }
-    },
     "require-directory": {
       "version": "2.1.1",
       "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
@@ -38343,28 +37756,11 @@
       "integrity": "sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw="
     },
     "srcset": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/srcset/-/srcset-2.0.1.tgz",
-      "integrity": "sha512-00kZI87TdRKwt+P8jj8UZxbfp7mK2ufxcIMWvhAOZNJTRROimpHeruWrGvCZneiuVDLqdyHefVp748ECTnyUBQ==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/srcset/-/srcset-5.0.0.tgz",
+      "integrity": "sha512-SqEZaAEhe0A6ETEa9O1IhSPC7MdvehZtCnTR0AftXk3QhY2UNgb+NApFOUPZILXk/YTDfFxMTNJOBpzrJsEdIA==",
       "optional": true
     },
-    "sshpk": {
-      "version": "1.17.0",
-      "resolved": "https://registry.npmjs.org/sshpk/-/sshpk-1.17.0.tgz",
-      "integrity": "sha512-/9HIEs1ZXGhSPE8X6Ccm7Nam1z8KcoCqPdI7ecm1N33EzAetWahvQWVqLZtaZQ+IDKX4IyA2o0gBzqIMkAagHQ==",
-      "optional": true,
-      "requires": {
-        "asn1": "~0.2.3",
-        "assert-plus": "^1.0.0",
-        "bcrypt-pbkdf": "^1.0.0",
-        "dashdash": "^1.12.0",
-        "ecc-jsbn": "~0.1.1",
-        "getpass": "^0.1.1",
-        "jsbn": "~0.1.0",
-        "safer-buffer": "^2.0.2",
-        "tweetnacl": "~0.14.0"
-      }
-    },
     "stack-utils": {
       "version": "2.0.5",
       "resolved": "https://registry.npmjs.org/stack-utils/-/stack-utils-2.0.5.tgz",
@@ -38794,28 +38190,48 @@
       "requires": {}
     },
     "superagent": {
-      "version": "6.1.0",
-      "resolved": "https://registry.npmjs.org/superagent/-/superagent-6.1.0.tgz",
-      "integrity": "sha512-OUDHEssirmplo3F+1HWKUrUjvnQuA+nZI6i/JJBdXb5eq9IyEQwPyPpqND+SSsxf6TygpBEkUjISVRN4/VOpeg==",
+      "version": "7.1.1",
+      "resolved": "https://registry.npmjs.org/superagent/-/superagent-7.1.1.tgz",
+      "integrity": "sha512-CQ2weSS6M+doIwwYFoMatklhRbx6sVNdB99OEJ5czcP3cng76Ljqus694knFWgOj3RkrtxZqIgpe6vhe0J7QWQ==",
       "dev": true,
       "requires": {
         "component-emitter": "^1.3.0",
-        "cookiejar": "^2.1.2",
-        "debug": "^4.1.1",
-        "fast-safe-stringify": "^2.0.7",
-        "form-data": "^3.0.0",
-        "formidable": "^1.2.2",
+        "cookiejar": "^2.1.3",
+        "debug": "^4.3.3",
+        "fast-safe-stringify": "^2.1.1",
+        "form-data": "^4.0.0",
+        "formidable": "^2.0.1",
         "methods": "^1.1.2",
-        "mime": "^2.4.6",
-        "qs": "^6.9.4",
+        "mime": "^2.5.0",
+        "qs": "^6.10.1",
         "readable-stream": "^3.6.0",
-        "semver": "^7.3.2"
+        "semver": "^7.3.5"
       },
       "dependencies": {
+        "debug": {
+          "version": "4.3.3",
+          "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.3.tgz",
+          "integrity": "sha512-/zxw5+vh1Tfv+4Qn7a5nsbcJKPaSvCDhojn6FEl9vupwK2VCSDtEiEtqr8DFtzYFOdz63LBkxec7DYuc2jon6Q==",
+          "dev": true,
+          "requires": {
+            "ms": "2.1.2"
+          }
+        },
+        "form-data": {
+          "version": "4.0.0",
+          "resolved": "https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz",
+          "integrity": "sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==",
+          "dev": true,
+          "requires": {
+            "asynckit": "^0.4.0",
+            "combined-stream": "^1.0.8",
+            "mime-types": "^2.1.12"
+          }
+        },
         "qs": {
-          "version": "6.10.1",
-          "resolved": "https://registry.npmjs.org/qs/-/qs-6.10.1.tgz",
-          "integrity": "sha512-M528Hph6wsSVOBiYUnGf+K/7w0hNshs/duGsNXPUCLH5XAqjEtiPGwNONLV0tBH8NoGb0mvD5JubnUTrujKDTg==",
+          "version": "6.10.3",
+          "resolved": "https://registry.npmjs.org/qs/-/qs-6.10.3.tgz",
+          "integrity": "sha512-wr7M2E0OFRfIfJZjKGieI8lBKb7fRCH4Fv5KNPEs7gJ8jadvotdsS08PzOKR7opXhZ/Xkjtt3WF9g38drmyRqQ==",
           "dev": true,
           "requires": {
             "side-channel": "^1.0.4"
@@ -38824,13 +38240,13 @@
       }
     },
     "supertest": {
-      "version": "6.1.6",
-      "resolved": "https://registry.npmjs.org/supertest/-/supertest-6.1.6.tgz",
-      "integrity": "sha512-0hACYGNJ8OHRg8CRITeZOdbjur7NLuNs0mBjVhdpxi7hP6t3QIbOzLON5RTUmZcy2I9riuII3+Pr2C7yztrIIg==",
+      "version": "6.2.2",
+      "resolved": "https://registry.npmjs.org/supertest/-/supertest-6.2.2.tgz",
+      "integrity": "sha512-wCw9WhAtKJsBvh07RaS+/By91NNE0Wh0DN19/hWPlBOU8tAfOtbZoVSV4xXeoKoxgPx0rx2y+y+8660XtE7jzg==",
       "dev": true,
       "requires": {
         "methods": "^1.1.2",
-        "superagent": "^6.1.0"
+        "superagent": "^7.1.0"
       }
     },
     "supports-color": {
@@ -39056,14 +38472,6 @@
       "integrity": "sha512-8hmiGIJMDlwjg7dlJ4yKGLK8EsYqKgPWbG3b4wjJddKNwc7N7Dpn08Df4szr/sZdMVeOstrdYSsqzX6BYbcB+w==",
       "dev": true
     },
-    "throng": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/throng/-/throng-5.0.0.tgz",
-      "integrity": "sha512-nrq7+qQhn/DL8yW/wiwImTepfi6ynOCAe7moSwgoYN1F32yQMdBkuFII40oAkb3cDfaL6q5BIoFTDCHdMWQ8Pw==",
-      "requires": {
-        "lodash": "^4.17.20"
-      }
-    },
     "through": {
       "version": "2.3.8",
       "resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
@@ -39277,17 +38685,11 @@
       "version": "0.6.0",
       "resolved": "https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz",
       "integrity": "sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=",
-      "devOptional": true,
+      "dev": true,
       "requires": {
         "safe-buffer": "^5.0.1"
       }
     },
-    "tweetnacl": {
-      "version": "0.14.5",
-      "resolved": "https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz",
-      "integrity": "sha1-WuaBd/GS1EViadEIr6k/+HQ/T2Q=",
-      "optional": true
-    },
     "type-check": {
       "version": "0.4.0",
       "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
@@ -39555,7 +38957,7 @@
       "version": "0.1.2",
       "resolved": "https://registry.npmjs.org/universalify/-/universalify-0.1.2.tgz",
       "integrity": "sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==",
-      "devOptional": true
+      "dev": true
     },
     "unpipe": {
       "version": "1.0.0",
@@ -39775,17 +39177,6 @@
       "resolved": "https://registry.npmjs.org/vary/-/vary-1.1.2.tgz",
       "integrity": "sha1-IpnwLG3tMNSllhsLn3RSShj2NPw="
     },
-    "verror": {
-      "version": "1.10.0",
-      "resolved": "https://registry.npmjs.org/verror/-/verror-1.10.0.tgz",
-      "integrity": "sha1-OhBcoXBTr1XW4nDB+CiGguGNpAA=",
-      "optional": true,
-      "requires": {
-        "assert-plus": "^1.0.0",
-        "core-util-is": "1.0.2",
-        "extsprintf": "^1.2.0"
-      }
-    },
     "vfile": {
       "version": "5.1.1",
       "resolved": "https://registry.npmjs.org/vfile/-/vfile-5.1.1.tgz",
@@ -40071,136 +39462,92 @@
       "peer": true
     },
     "website-scraper": {
-      "version": "4.2.3",
-      "resolved": "https://registry.npmjs.org/website-scraper/-/website-scraper-4.2.3.tgz",
-      "integrity": "sha512-Pqrirzwt02NtaTFkBulF3fGSvPGOAVpdwPFHzoh49gFjU2GgaEgoW8WMlhPbzRcQkd6+XmsU+LZeW9SiluDHkA==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/website-scraper/-/website-scraper-5.0.0.tgz",
+      "integrity": "sha512-wZP7fSQR86UZSCXfKzd5OlgBb6AdxXN6gVN07Hy2wYxp2+GeqQAIw+sbqXNlPQnpJLwmRZDWp2u6KeuaFOhotw==",
       "optional": true,
       "requires": {
-        "bluebird": "^3.0.1",
-        "cheerio": "0.22.0",
+        "cheerio": "1.0.0-rc.10",
         "css-url-parser": "^1.0.0",
-        "debug": "^4.0.1",
-        "fs-extra": "^8.0.1",
-        "he": "^1.1.0",
-        "lodash": "^4.17.20",
-        "normalize-url": "^4.0.0",
-        "p-queue": "^6.6.1",
-        "request": "^2.85.0",
+        "debug": "^4.3.1",
+        "fs-extra": "^10.0.0",
+        "got": "^12.0.0",
+        "lodash": "^4.17.21",
+        "normalize-url": "^7.0.2",
+        "p-queue": "^7.1.0",
         "sanitize-filename": "^1.6.3",
-        "srcset": "^2.0.0"
+        "srcset": "^5.0.0"
       },
       "dependencies": {
-        "cheerio": {
-          "version": "0.22.0",
-          "resolved": "https://registry.npmjs.org/cheerio/-/cheerio-0.22.0.tgz",
-          "integrity": "sha1-qbqoYKP5tZWmuBsahocxIe06Jp4=",
+        "@szmarczak/http-timer": {
+          "version": "5.0.1",
+          "resolved": "https://registry.npmjs.org/@szmarczak/http-timer/-/http-timer-5.0.1.tgz",
+          "integrity": "sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw==",
           "optional": true,
           "requires": {
-            "css-select": "~1.2.0",
-            "dom-serializer": "~0.1.0",
-            "entities": "~1.1.1",
-            "htmlparser2": "^3.9.1",
-            "lodash.assignin": "^4.0.9",
-            "lodash.bind": "^4.1.4",
-            "lodash.defaults": "^4.0.1",
-            "lodash.filter": "^4.4.0",
-            "lodash.flatten": "^4.2.0",
-            "lodash.foreach": "^4.3.0",
-            "lodash.map": "^4.4.0",
-            "lodash.merge": "^4.4.0",
-            "lodash.pick": "^4.2.1",
-            "lodash.reduce": "^4.4.0",
-            "lodash.reject": "^4.4.0",
-            "lodash.some": "^4.4.0"
+            "defer-to-connect": "^2.0.1"
           }
         },
-        "css-select": {
-          "version": "1.2.0",
-          "resolved": "https://registry.npmjs.org/css-select/-/css-select-1.2.0.tgz",
-          "integrity": "sha1-KzoRBTnFNV8c2NMUYj6HCxIeyFg=",
-          "optional": true,
-          "requires": {
-            "boolbase": "~1.0.0",
-            "css-what": "2.1",
-            "domutils": "1.5.1",
-            "nth-check": "~1.0.1"
-          }
-        },
-        "css-what": {
-          "version": "2.1.3",
-          "resolved": "https://registry.npmjs.org/css-what/-/css-what-2.1.3.tgz",
-          "integrity": "sha512-a+EPoD+uZiNfh+5fxw2nO9QwFa6nJe2Or35fGY6Ipw1R3R4AGz1d1TEZrCegvw2YTmZ0jXirGYlzxxpYSHwpEg==",
+        "cacheable-lookup": {
+          "version": "6.0.4",
+          "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-6.0.4.tgz",
+          "integrity": "sha512-mbcDEZCkv2CZF4G01kr8eBd/5agkt9oCqz75tJMSIsquvRZ2sL6Hi5zGVKi/0OSC9oO1GHfJ2AV0ZIOY9vye0A==",
           "optional": true
         },
-        "dom-serializer": {
-          "version": "0.1.1",
-          "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-0.1.1.tgz",
-          "integrity": "sha512-l0IU0pPzLWSHBcieZbpOKgkIn3ts3vAh7ZuFyXNwJxJXk/c4Gwj9xaTJwIDVQCXawWD0qb3IzMGH5rglQaO0XA==",
-          "optional": true,
-          "requires": {
-            "domelementtype": "^1.3.0",
-            "entities": "^1.1.1"
-          }
-        },
-        "domelementtype": {
-          "version": "1.3.1",
-          "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-1.3.1.tgz",
-          "integrity": "sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==",
+        "get-stream": {
+          "version": "6.0.1",
+          "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz",
+          "integrity": "sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==",
           "optional": true
         },
-        "domhandler": {
-          "version": "2.4.2",
-          "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-2.4.2.tgz",
-          "integrity": "sha512-JiK04h0Ht5u/80fdLMCEmV4zkNh2BcoMFBmZ/91WtYZ8qVXSKjiw7fXMgFPnHcSZgOo3XdinHvmnDUeMf5R4wA==",
+        "got": {
+          "version": "12.0.1",
+          "resolved": "https://registry.npmjs.org/got/-/got-12.0.1.tgz",
+          "integrity": "sha512-1Zhoh+lDej3t7Ks1BP/Jufn+rNqdiHQgUOcTxHzg2Dao1LQfp5S4Iq0T3iBxN4Zdo7QqCJL+WJUNzDX6rCP2Ew==",
           "optional": true,
           "requires": {
-            "domelementtype": "1"
+            "@sindresorhus/is": "^4.2.0",
+            "@szmarczak/http-timer": "^5.0.1",
+            "@types/cacheable-request": "^6.0.2",
+            "@types/responselike": "^1.0.0",
+            "cacheable-lookup": "^6.0.4",
+            "cacheable-request": "^7.0.2",
+            "decompress-response": "^6.0.0",
+            "form-data-encoder": "1.7.1",
+            "get-stream": "^6.0.1",
+            "http2-wrapper": "^2.1.9",
+            "lowercase-keys": "^3.0.0",
+            "p-cancelable": "^3.0.0",
+            "responselike": "^2.0.0"
           }
         },
-        "domutils": {
-          "version": "1.5.1",
-          "resolved": "https://registry.npmjs.org/domutils/-/domutils-1.5.1.tgz",
-          "integrity": "sha1-3NhIiib1Y9YQeeSMn3t+Mjc2gs8=",
+        "http2-wrapper": {
+          "version": "2.1.10",
+          "resolved": "https://registry.npmjs.org/http2-wrapper/-/http2-wrapper-2.1.10.tgz",
+          "integrity": "sha512-QHgsdYkieKp+6JbXP25P+tepqiHYd+FVnDwXpxi/BlUcoIB0nsmTOymTNvETuTO+pDuwcSklPE72VR3DqV+Haw==",
           "optional": true,
           "requires": {
-            "dom-serializer": "0",
-            "domelementtype": "1"
+            "quick-lru": "^5.1.1",
+            "resolve-alpn": "^1.2.0"
           }
         },
-        "entities": {
-          "version": "1.1.2",
-          "resolved": "https://registry.npmjs.org/entities/-/entities-1.1.2.tgz",
-          "integrity": "sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==",
+        "lowercase-keys": {
+          "version": "3.0.0",
+          "resolved": "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-3.0.0.tgz",
+          "integrity": "sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ==",
           "optional": true
         },
-        "htmlparser2": {
-          "version": "3.10.1",
-          "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-3.10.1.tgz",
-          "integrity": "sha512-IgieNijUMbkDovyoKObU1DUhm1iwNYE/fuifEoEHfd1oZKZDaONBSkal7Y01shxsM49R4XaMdGez3WnF9UfiCQ==",
-          "optional": true,
-          "requires": {
-            "domelementtype": "^1.3.1",
-            "domhandler": "^2.3.0",
-            "domutils": "^1.5.1",
-            "entities": "^1.1.1",
-            "inherits": "^2.0.1",
-            "readable-stream": "^3.1.1"
-          }
-        },
         "normalize-url": {
-          "version": "4.5.1",
-          "resolved": "https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.1.tgz",
-          "integrity": "sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==",
+          "version": "7.0.3",
+          "resolved": "https://registry.npmjs.org/normalize-url/-/normalize-url-7.0.3.tgz",
+          "integrity": "sha512-RiCOdwdPnzvwcBFJE4iI1ss3dMVRIrEzFpn8ftje6iBfzBInqlnRrNhxcLwBEKjPPXQKzm1Ptlxtaiv9wdcj5w==",
           "optional": true
         },
-        "nth-check": {
-          "version": "1.0.2",
-          "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz",
-          "integrity": "sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==",
-          "optional": true,
-          "requires": {
-            "boolbase": "~1.0.0"
-          }
+        "p-cancelable": {
+          "version": "3.0.0",
+          "resolved": "https://registry.npmjs.org/p-cancelable/-/p-cancelable-3.0.0.tgz",
+          "integrity": "sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==",
+          "optional": true
         }
       }
     },
@@ -40452,12 +39799,6 @@
         "fd-slicer": "~1.1.0"
       }
     },
-    "yesno": {
-      "version": "0.3.1",
-      "resolved": "https://registry.npmjs.org/yesno/-/yesno-0.3.1.tgz",
-      "integrity": "sha512-7RbCXegyu6DykWPWU0YEtW8gFJH8KBL2d5l2fqB0XpkH0Y9rk59YSSWpzEv7yNJBGAouPc67h3kkq0CZkpBdFw==",
-      "dev": true
-    },
     "yocto-queue": {
       "version": "0.1.0",
       "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
diff --git a/package.json b/package.json
index 086ad8f383..3bb926b7f4 100644
--- a/package.json
+++ b/package.json
@@ -87,7 +87,6 @@
     "strip-html-comments": "^1.0.0",
     "styled-components": "^5.3.3",
     "swr": "1.1.2",
-    "throng": "^5.0.0",
     "ts-dedent": "^2.2.0",
     "unified": "^10.1.0",
     "unist-util-visit": "^4.1.0",
@@ -166,10 +165,9 @@
     "sass": "^1.49.0",
     "start-server-and-test": "^1.14.0",
     "strip-ansi": "^7.0.1",
-    "supertest": "^6.1.6",
+    "supertest": "^6.2.2",
     "typescript": "^4.5.5",
-    "url-template": "^3.0.0",
-    "yesno": "^0.3.1"
+    "url-template": "^3.0.0"
   },
   "engines": {
     "node": "16.x"
@@ -186,14 +184,14 @@
     "jimp": "^0.16.1",
     "pa11y-ci": "^2.4.2",
     "puppeteer": "^9.1.1",
-    "website-scraper": "^4.2.3",
+    "website-scraper": "^5.0.0",
     "xlsx-populate": "^1.21.0"
   },
   "private": true,
   "repository": "https://github.com/github/docs",
   "scripts": {
     "browser-test": "start-server-and-test browser-test-server 4001 browser-test-tests",
-    "browser-test-server": "cross-env NODE_ENV=production WEB_CONCURRENCY=1 PORT=4001 ENABLED_LANGUAGES=en,ja node server.mjs",
+    "browser-test-server": "cross-env NODE_ENV=production PORT=4001 ENABLED_LANGUAGES=en,ja node server.mjs",
     "browser-test-tests": "cross-env BROWSER=1 NODE_OPTIONS=--experimental-vm-modules jest tests/browser/browser.js",
     "build": "next build",
     "debug": "cross-env NODE_ENV=development ENABLED_LANGUAGES='en,ja' nodemon --inspect server.mjs",
@@ -214,7 +212,7 @@
     "sync-search": "cross-env NODE_OPTIONS='--max_old_space_size=8192' start-server-and-test sync-search-server 4002 sync-search-indices",
     "sync-search-ghes-release": "cross-env GHES_RELEASE=1 start-server-and-test sync-search-server 4002 sync-search-indices",
     "sync-search-indices": "script/sync-search-indices.js",
-    "sync-search-server": "cross-env NODE_ENV=production WEB_CONCURRENCY=1 PORT=4002 node server.mjs",
+    "sync-search-server": "cross-env NODE_ENV=production PORT=4002 node server.mjs",
     "translation-check": "start-server-and-test translation-check-server 4002 translation-check-test",
     "translation-check-server": "cross-env NODE_ENV=test PORT=4002 node server.mjs",
     "translation-check-test": "script/i18n/test-html-pages.js",
diff --git a/script/README.md b/script/README.md
index 2d10e88d81..c156ae0fd5 100644
--- a/script/README.md
+++ b/script/README.md
@@ -99,14 +99,6 @@ This script is run automatically when you run the server locally. It checks whet
 
 This script turns a Google Sheets CSV spreadsheet into a YAML file.
 
----
-
-
-### [`deploy.js`](deploy.js)
-
-This script enables us to execute both staging and production deployments from our local machine (in case GitHub Actions is unavailable). :rocket:
-
-:warning: Deploy to production only with maximum caution!
 
 ---
 
diff --git a/script/deploy.js b/script/deploy.js
deleted file mode 100755
index 6c60c61065..0000000000
--- a/script/deploy.js
+++ /dev/null
@@ -1,258 +0,0 @@
-#!/usr/bin/env node
-
-// [start-readme]
-//
-// This script is run by a GitHub Actions workflow to trigger deployments
-// to Heroku for both staging and production apps.
-//
-// You can also run it locally if you:
-//  - Supply a GitHub PAT as the GITHUB_TOKEN environment variable
-//  - Supply a Heroku API token as the HEROKU_API_TOKEN environment variable
-//  - Optionally, supply a GitHub PAT as the DOCUBOT_REPO_PAT environment
-//    variable if you want to support content from the `docs-early-access` repo
-//
-// For production deployment in particular, you MUST:
-//  - Provide the name of the Heroku App we use for production as the
-//    HEROKU_PRODUCTION_APP_NAME environment variable. This must be obfuscated
-//    from our codebase for security reasons.
-//
-// ...and you SHOULD:
-//  - Supply the aforementioned DOCUBOT_REPO_PAT environment variable to support
-//    content from the `docs-early-access` repo. In most cases, you should be
-//    able to just set this to the same value as GITHUB_TOKEN when running this
-//    script locally as it just needs read access to that repo.
-//  - Supply our Fastly API token and Service ID as the FASTLY_TOKEN and
-//    FASTLY_SERVICE_ID enviroment variables, respectively, to support
-//    soft-purging the Fastly cache after deploying.
-//
-// Examples:
-//  - Deploy a PR to Staging and force the Heroku App to be rebuilt from scratch (by default):
-//      script/deploy.js --staging https://github.com/github/docs/pull/9876
-//
-//  - Deploy a PR to Staging and DO NOT rebuild the Heroku App:
-//      script/deploy.js --staging https://github.com/github/docs-internal/pull/12345 --no-rebuild
-//
-//  - Deploy the latest from docs-internal `main` to production:
-//      script/deploy.js --production
-//
-// [end-readme]
-
-import dotenv from 'dotenv'
-import program from 'commander'
-import { has } from 'lodash-es'
-import yesno from 'yesno'
-import getOctokit from './helpers/github.js'
-import parsePrUrl from './deployment/parse-pr-url.js'
-import deployToStaging from './deployment/deploy-to-staging.js'
-import deployToProduction from './deployment/deploy-to-production.js'
-import purgeEdgeCache from './deployment/purge-edge-cache.js'
-
-dotenv.config()
-
-const { GITHUB_TOKEN, HEROKU_API_TOKEN } = process.env
-
-// Exit if GitHub Actions PAT is not found
-if (!GITHUB_TOKEN) {
-  throw new Error('You must supply a GITHUB_TOKEN environment variable!')
-}
-
-// Exit if Heroku API token is not found
-if (!HEROKU_API_TOKEN) {
-  throw new Error('You must supply a HEROKU_API_TOKEN environment variable!')
-}
-
-const STAGING_FLAG = '--staging'
-const PRODUCTION_FLAG = '--production'
-const ALLOWED_OWNER = 'github'
-const ALLOWED_SOURCE_REPOS = ['docs', 'docs-internal']
-const EXPECTED_PR_URL_FORMAT = `https://github.com/${ALLOWED_OWNER}/(${ALLOWED_SOURCE_REPOS.join(
-  '|'
-)})/pull/123`
-
-program
-  .description('Trigger a deployment to Heroku for either staging or production apps')
-  .option(PRODUCTION_FLAG, 'Deploy the latest internal main branch to Production')
-  .option(`${STAGING_FLAG} <PR_URL>`, 'Deploy a pull request to Staging')
-  .option(
-    '--no-rebuild',
-    'Do NOT force a Staging deployment to rebuild the Heroku App from scratch'
-  )
-  .parse(process.argv)
-
-const opts = program.opts()
-const isProduction = opts.production === true
-const isStaging = has(opts, 'staging')
-const prUrl = opts.staging
-const forceRebuild = !isProduction && opts.rebuild !== false
-
-//
-// Verify CLI options
-//
-if (!isProduction && !isStaging) {
-  invalidateAndExit(
-    'commander.missingArgument',
-    `error: must specify option '${STAGING_FLAG} <PR_URL>' or '${PRODUCTION_FLAG}'`
-  )
-}
-
-if (isProduction && isStaging) {
-  invalidateAndExit(
-    'commander.conflictingArgument',
-    `error: must specify option '${STAGING_FLAG} <PR_URL>' or '${PRODUCTION_FLAG}' but not both`
-  )
-}
-
-if (isProduction && forceRebuild) {
-  invalidateAndExit(
-    'commander.conflictingArgument',
-    `error: cannot specify option '--rebuild' combined with option '${PRODUCTION_FLAG}'`
-  )
-}
-
-// Extract the repository name and pull request number from the URL (if any)
-const { owner, repo, pullNumber } = parsePrUrl(prUrl)
-
-if (isStaging) {
-  if (owner !== ALLOWED_OWNER || !ALLOWED_SOURCE_REPOS.includes(repo) || !pullNumber) {
-    invalidateAndExit(
-      'commander.invalidArgument',
-      `error: option '${STAGING_FLAG}' argument '${prUrl}' is invalid.
-Must match URL format '${EXPECTED_PR_URL_FORMAT}'`
-    )
-  }
-}
-
-deploy()
-
-//
-// Function definitions
-//
-
-function invalidateAndExit(errorType, message) {
-  program._displayError(1, errorType, message)
-  process.exit(1)
-}
-
-async function deploy() {
-  if (isProduction) {
-    await deployProduction()
-  } else if (isStaging) {
-    await deployStaging({ owner, repo, pullNumber, forceRebuild })
-  }
-}
-
-async function deployProduction() {
-  const { HEROKU_PRODUCTION_APP_NAME, DOCUBOT_REPO_PAT, FASTLY_TOKEN, FASTLY_SERVICE_ID } =
-    process.env
-
-  // Exit if Heroku App name is not found
-  if (!HEROKU_PRODUCTION_APP_NAME) {
-    throw new Error('You must supply a HEROKU_PRODUCTION_APP_NAME environment variable!')
-  }
-
-  // Warn if @docubot PAT is not found
-  if (!DOCUBOT_REPO_PAT) {
-    console.warn(
-      '⚠️ You did not supply a DOCUBOT_REPO_PAT environment variable.\nWithout it, this deployment will not contain any Early Access content!'
-    )
-  }
-
-  // Warn if Fastly credentials are not found
-  if (!FASTLY_TOKEN) {
-    console.warn(
-      '⚠️ You did not supply a FASTLY_TOKEN environment variable.\nWithout it, this deployment will not soft-purge the Fastly cache!'
-    )
-  }
-  if (!FASTLY_SERVICE_ID) {
-    console.warn(
-      '⚠️ You did not supply a FASTLY_SERVICE_ID environment variable.\nWithout it, this deployment will not soft-purge the Fastly cache!'
-    )
-  }
-  if (!process.env.FASTLY_SURROGATE_KEY) {
-    // Default to our current Fastly surrogate key if unspecified
-    process.env.FASTLY_SURROGATE_KEY = 'all-the-things'
-  }
-
-  // Request confirmation before deploying to production
-  const proceed = await yesno({
-    question: '\n🛑 You have selected to deploy to production. ARE YOU CERTAIN!?',
-    defaultValue: null,
-  })
-
-  if (!proceed) {
-    console.error('\n❌ User canceled the production deployment! Halting...')
-    process.exit(1)
-  }
-
-  // This helper uses the `GITHUB_TOKEN` implicitly
-  const octokit = getOctokit()
-
-  try {
-    await deployToProduction({
-      octokit,
-      includeDelayForPreboot: !!(FASTLY_TOKEN && FASTLY_SERVICE_ID),
-    })
-
-    await purgeEdgeCache()
-  } catch (error) {
-    console.error(`Failed to deploy production: ${error.message}`)
-    console.error(error)
-    process.exit(1)
-  }
-}
-
-async function deployStaging({ owner, repo, pullNumber, forceRebuild = false }) {
-  // Hardcode the Status context name to match Actions
-  const CONTEXT_NAME = 'Staging - Deploy PR / deploy (pull_request)'
-
-  // This helper uses the `GITHUB_TOKEN` implicitly
-  const octokit = getOctokit()
-
-  const { data: pullRequest } = await octokit.pulls.get({
-    owner,
-    repo,
-    pull_number: pullNumber,
-  })
-
-  try {
-    await octokit.repos.createCommitStatus({
-      owner,
-      repo,
-      sha: pullRequest.head.sha,
-      context: CONTEXT_NAME,
-      state: 'pending',
-      description: 'The app is being deployed. See local logs.',
-    })
-
-    await deployToStaging({
-      octokit,
-      pullRequest,
-      forceRebuild,
-    })
-
-    await octokit.repos.createCommitStatus({
-      owner,
-      repo,
-      sha: pullRequest.head.sha,
-      context: CONTEXT_NAME,
-      state: 'success',
-      description: 'Successfully deployed! See local logs.',
-    })
-  } catch (error) {
-    console.error(`Failed to deploy to staging: ${error.message}`)
-    console.error(error)
-
-    await octokit.repos.createCommitStatus({
-      owner,
-      repo,
-      sha: pullRequest.head.sha,
-      context: CONTEXT_NAME,
-      state: 'error',
-      description: 'Failed to deploy. See local logs.',
-    })
-
-    process.exit(1)
-  }
-}
-
-export default deploy
diff --git a/server.mjs b/server.mjs
index 5f082cf182..fa4bb2c0fe 100644
--- a/server.mjs
+++ b/server.mjs
@@ -2,37 +2,20 @@ import dotenv from 'dotenv'
 import './lib/feature-flags.js'
 import './lib/check-node-version.js'
 import './lib/handle-exceptions.js'
-import throng from 'throng'
-import os from 'os'
 import portUsed from 'port-used'
-import prefixStreamWrite from './lib/prefix-stream-write.js'
 import createApp from './lib/app.js'
 import warmServer from './lib/warm-server.js'
 import http from 'http'
 dotenv.config()
-// Intentionally require these for both cluster primary and workers
 
 const { PORT, NODE_ENV } = process.env
 const port = Number(PORT) || 4000
 
-// Start the server!
-if (NODE_ENV === 'production') {
-  clusteredMain()
-} else {
-  nonClusteredMain()
-}
+async function main() {
+  if (NODE_ENV !== 'production') {
+    await checkPortAvailability()
+  }
 
-function clusteredMain() {
-  // Spin up a cluster!
-  throng({
-    master: setupPrimary,
-    worker: setupWorker,
-    count: calculateWorkerCount(),
-  })
-}
-
-async function nonClusteredMain() {
-  await checkPortAvailability()
   await startServer()
 }
 
@@ -69,68 +52,4 @@ async function startServer() {
     .on('error', () => server.close())
 }
 
-// This function will only be run in the primary process
-async function setupPrimary() {
-  process.on('beforeExit', () => {
-    console.log('Shutting down primary...')
-    console.log('Exiting!')
-  })
-
-  console.log('Starting up primary...')
-
-  await checkPortAvailability()
-}
-
-// IMPORTANT: This function will be run in a separate worker process!
-async function setupWorker(id, disconnect) {
-  let exited = false
-
-  // Wrap stdout and stderr to include the worker ID as a static prefix
-  // console.log('hi') => '[worker.1]: hi'
-  const prefix = `[worker.${id}]: `
-  prefixStreamWrite(process.stdout, prefix)
-  prefixStreamWrite(process.stderr, prefix)
-
-  process.on('beforeExit', () => {
-    console.log('Exiting!')
-  })
-
-  process.on('SIGTERM', shutdown)
-  process.on('SIGINT', shutdown)
-
-  console.log('Starting up worker...')
-
-  // Load the server in each worker process and share the port via sharding
-  await startServer()
-
-  function shutdown() {
-    if (exited) return
-    exited = true
-
-    console.log('Shutting down worker...')
-    disconnect()
-  }
-}
-
-function calculateWorkerCount() {
-  // Heroku's recommended WEB_CONCURRENCY count based on the WEB_MEMORY config,
-  // or explicitly configured by us
-  const { WEB_CONCURRENCY } = process.env
-
-  const recommendedCount = parseInt(WEB_CONCURRENCY, 10)
-  const cpuCount = os.cpus().length
-
-  // Ensure the recommended count is AT LEAST 1 for safety
-  let workerCount = Math.max(recommendedCount || 1, 1)
-
-  // If WEB_CONCURRENCY value was configured to a valid number...
-  if (recommendedCount > 0) {
-    // Use the smaller value between the recommendation vs. the CPU count
-    workerCount = Math.min(workerCount, cpuCount)
-  } else if (NODE_ENV === 'production') {
-    // Else if in a deployed environment, default to the CPU count
-    workerCount = cpuCount
-  }
-
-  return workerCount
-}
+main()
diff --git a/tests/content/search.js b/tests/content/search.js
index 00b21d9544..e212edbbaf 100644
--- a/tests/content/search.js
+++ b/tests/content/search.js
@@ -1,8 +1,11 @@
+import { jest, describe, expect } from '@jest/globals'
+
 import { dates, supported } from '../../lib/enterprise-server-releases.js'
 import libLanguages from '../../lib/languages.js'
 import { namePrefix } from '../../lib/search/config.js'
-import { expect } from '@jest/globals'
 import lunrIndexNames from '../../script/search/lunr-get-index-names.js'
+import { get } from '../helpers/supertest.js'
+
 const languageCodes = Object.keys(libLanguages)
 
 describe('search', () => {
@@ -44,3 +47,49 @@ function getDate(date) {
   const dateObj = date ? new Date(date) : new Date()
   return dateObj.toISOString().slice(0, 10)
 }
+
+describe('search middleware', () => {
+  jest.setTimeout(60 * 1000)
+
+  test('basic search', async () => {
+    const sp = new URLSearchParams()
+    sp.set('query', 'stuff')
+    sp.set('language', 'en')
+    sp.set('version', 'dotcom')
+    const res = await get('/search?' + sp)
+    expect(res.statusCode).toBe(200)
+    const results = JSON.parse(res.text)
+    expect(Array.isArray(results)).toBeTruthy()
+  })
+
+  test('limit search', async () => {
+    const sp = new URLSearchParams()
+    sp.set('query', 'github') // will yield lots of results
+    sp.set('language', 'en')
+    sp.set('version', 'dotcom')
+    sp.set('limit', '1')
+    const res = await get('/search?' + sp)
+    expect(res.statusCode).toBe(200)
+    const results = JSON.parse(res.text)
+    expect(Array.isArray(results)).toBeTruthy()
+    expect(results.length).toBe(1)
+  })
+
+  test('invalid search version', async () => {
+    const sp = new URLSearchParams()
+    sp.set('query', 'stuff')
+    sp.set('language', 'en')
+    sp.set('version', 'NEVERHEARDOF')
+    const res = await get('/search?' + sp)
+    expect(res.statusCode).toBe(400)
+  })
+
+  test('invalid search language', async () => {
+    const sp = new URLSearchParams()
+    sp.set('query', 'stuff')
+    sp.set('language', 'NEVERHEARDOF')
+    sp.set('version', 'dotcom')
+    const res = await get('/search?' + sp)
+    expect(res.statusCode).toBe(400)
+  })
+})
diff --git a/tests/fixtures/page-with-optional-attributes.md b/tests/fixtures/page-with-optional-attributes.md
new file mode 100644
index 0000000000..2785cda4d9
--- /dev/null
+++ b/tests/fixtures/page-with-optional-attributes.md
@@ -0,0 +1,12 @@
+---
+title: My attributes are empty if not FPT
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+product: '{% ifversion fpt %}FPT rulez!{% endif %}'
+permissions: '{% ifversion fpt %}FPT only!{% endif %}'
+---
+
+No content really.
diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js
index dbe5715ec0..033039d3f3 100644
--- a/tests/meta/repository-references.js
+++ b/tests/meta/repository-references.js
@@ -67,7 +67,6 @@ const ALLOW_DOCS_PATHS = [
   'ownership.yaml',
   'docs/index.yaml',
   'lib/excluded-links.js',
-  'script/deploy.js',
   'script/README.md',
   'script/toggle-ghae-feature-flags.js',
   '.github/workflows/hubber-contribution-help.yml',
diff --git a/tests/rendering/server.js b/tests/rendering/server.js
index 9bda85f634..c47dd24d14 100644
--- a/tests/rendering/server.js
+++ b/tests/rendering/server.js
@@ -1034,7 +1034,16 @@ describe('static routes', () => {
     expect(res.headers['set-cookie']).toBeUndefined()
     expect(res.headers['cache-control']).toContain('public')
     expect(res.headers['cache-control']).toMatch(/max-age=\d+/)
-    expect(res.headers['surrogate-key']).toBeTruthy()
+    expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.MANUAL)
+  })
+
+  it('no manual surrogate key for /assets requests without caching-busting prefix', async () => {
+    const res = await get('/assets/images/site/be-social.gif')
+    expect(res.statusCode).toBe(200)
+    expect(res.headers['set-cookie']).toBeUndefined()
+    expect(res.headers['cache-control']).toContain('public')
+    expect(res.headers['cache-control']).toMatch(/max-age=\d+/)
+    expect(res.headers['surrogate-key']).toBe(SURROGATE_ENUMS.DEFAULT)
   })
 
   it('serves schema files from the /data/graphql directory at /public', async () => {
diff --git a/tests/unit/load-translation-orphans.js b/tests/unit/load-translation-orphans.js
new file mode 100644
index 0000000000..581c6ee23c
--- /dev/null
+++ b/tests/unit/load-translation-orphans.js
@@ -0,0 +1,60 @@
+import path from 'path'
+import { fileURLToPath } from 'url'
+
+import { expect } from '@jest/globals'
+
+import languages from '../../lib/languages.js'
+import Page from '../../lib/page.js'
+import { loadPageMap, correctTranslationOrphans } from '../../lib/page-data.js'
+const __dirname = path.dirname(fileURLToPath(import.meta.url))
+
+describe('loading page map with translation orphans', () => {
+  test('inject missing translations from English', async () => {
+    const basePath = path.join(__dirname, '../fixtures')
+    const page = await Page.init({
+      relativePath: 'page-that-does-not-exist-in-translations-dir.md',
+      basePath,
+      languageCode: 'en',
+    })
+    console.assert(page, 'page could not be loaded')
+
+    const pageList = [page]
+    const pageMap = await loadPageMap(await correctTranslationOrphans(pageList, basePath))
+    // It should make a copy of the English into each language
+    expect(Object.keys(pageMap).length).toBe(Object.keys(languages).length)
+
+    // +1 for the test just above, 2 tests per language.
+    expect.assertions(1 + Object.keys(languages).length * 2)
+
+    for (const languageCode of Object.keys(languages)) {
+      for (const permalink of page.permalinks) {
+        const translationHref = permalink.href.replace('/en', `/${languageCode}`)
+        const translationPage = pageMap[translationHref]
+        expect(translationPage).toBeTruthy()
+        expect(translationPage.languageCode).toBe(languageCode)
+      }
+    }
+  })
+
+  test('remove translation pages that were not in English', async () => {
+    const basePath = path.join(__dirname, '../fixtures')
+    const page = await Page.init({
+      relativePath: 'page-that-does-not-exist-in-translations-dir.md',
+      basePath,
+      languageCode: 'en',
+    })
+    console.assert(page, 'page could not be loaded')
+    const orphan = await Page.init({
+      relativePath: 'article-with-videos.md',
+      basePath,
+      languageCode: 'ja',
+    })
+    console.assert(orphan, 'page could not be loaded')
+    const orphanPermalinks = orphan.permalinks.map((p) => p.href)
+
+    const pageList = await correctTranslationOrphans([page, orphan], basePath)
+    const pageMap = await loadPageMap(pageList)
+    expect(pageMap[orphanPermalinks[0]]).toBeFalsy()
+    expect(Object.keys(pageMap).length).toBe(Object.keys(languages).length)
+  })
+})
diff --git a/tests/unit/page.js b/tests/unit/page.js
index 9f22398d2d..8ee036dba4 100644
--- a/tests/unit/page.js
+++ b/tests/unit/page.js
@@ -1,12 +1,14 @@
 import { fileURLToPath } from 'url'
 import path from 'path'
 import cheerio from 'cheerio'
+import { describe, expect } from '@jest/globals'
+
 import Page from '../../lib/page.js'
 import readJsonFile from '../../lib/read-json-file.js'
 import { allVersions } from '../../lib/all-versions.js'
 import enterpriseServerReleases, { latest } from '../../lib/enterprise-server-releases.js'
 import nonEnterpriseDefaultVersion from '../../lib/non-enterprise-default-version.js'
-// import getLinkData from '../../lib/get-link-data.js'
+
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
 const prerenderedObjects = readJsonFile('./lib/graphql/static/prerendered-objects.json')
 const enterpriseServerVersions = Object.keys(allVersions).filter((v) =>
@@ -766,4 +768,35 @@ describe('catches errors thrown in Page class', () => {
       /`versions` frontmatter.*? product is not available in/
     )
   })
+
+  describe('versionining optional attributes', () => {
+    test("re-rendering set appropriate 'product', 'permissions', 'learningTracks'", async () => {
+      const page = await Page.init({
+        relativePath: 'page-with-optional-attributes.md',
+        basePath: path.join(__dirname, '../fixtures'),
+        languageCode: 'en',
+      })
+      const context = {
+        page: { version: `enterprise-server@3.2` },
+        currentVersion: `enterprise-server@3.2`,
+        currentProduct: 'snowbird',
+        currentLanguage: 'en',
+        currentPath: '/en/enterprise-server@3.2/optional/attributes',
+        fpt: false, // what the shortVersions contextualizer does
+      }
+
+      await page.render(context)
+      expect(page.product).toBe('')
+      expect(page.permissions).toBe('')
+
+      // Change to FPT
+      context.page.version = nonEnterpriseDefaultVersion
+      context.version = nonEnterpriseDefaultVersion
+      context.currentPath = '/en/optional/attributes'
+      context.fpt = true
+      await page.render(context)
+      expect(page.product).toContain('FPT rulez!')
+      expect(page.permissions).toContain('FPT only!')
+    })
+  })
 })
diff --git a/tests/unit/pages.js b/tests/unit/pages.js
index 4a8f045417..fe66b9456c 100644
--- a/tests/unit/pages.js
+++ b/tests/unit/pages.js
@@ -1,6 +1,6 @@
 import { jest } from '@jest/globals'
 import path from 'path'
-import { loadPages, loadPageMap } from '../../lib/page-data.js'
+import { loadPages, loadPageMap, correctTranslationOrphans } from '../../lib/page-data.js'
 import libLanguages from '../../lib/languages.js'
 import { liquid } from '../../lib/render-content/index.js'
 import patterns from '../../lib/patterns.js'
@@ -13,13 +13,24 @@ import removeFPTFromPath from '../../lib/remove-fpt-from-path.js'
 const languageCodes = Object.keys(libLanguages)
 const slugger = new GithubSlugger()
 
+// By default, the tests don't change that each translation has an
+// equivalent English page (e.g. `translations/*/content/foo.md`
+// expects `content/foo.md`)
+// Set the environment variable `TEST_TRANSLATION_MATCHING=true`
+// to enable that test.
+const testIfRequireTranslationMatching = JSON.parse(
+  process.env.TEST_TRANSLATION_MATCHING || 'false'
+)
+  ? test
+  : test.skip
+
 describe('pages module', () => {
   jest.setTimeout(60 * 1000)
 
   let pages
 
   beforeAll(async () => {
-    pages = await loadPages()
+    pages = await correctTranslationOrphans(await loadPages())
   })
 
   describe('loadPages', () => {
@@ -76,8 +87,8 @@ describe('pages module', () => {
 
       const message = `Found ${duplicates.length} duplicate redirect_from ${
         duplicates.length === 1 ? 'path' : 'paths'
-      }. 
-      Ensure that you don't define the same path more than once in the redirect_from property in a single file and across all English files. 
+      }.
+      Ensure that you don't define the same path more than once in the redirect_from property in a single file and across all English files.
       You may also receive this error if you have defined the same children property more than once.\n
   ${duplicates.join('\n')}`
       expect(duplicates.length, message).toBe(0)
@@ -152,26 +163,29 @@ describe('pages module', () => {
       expect(liquidErrors.length, failureMessage).toBe(0)
     })
 
-    test('every non-English page has a matching English page', async () => {
-      const englishPaths = chain(walk('content', { directories: false }))
-        .uniq()
-        .value()
+    testIfRequireTranslationMatching(
+      'every non-English page has a matching English page',
+      async () => {
+        const englishPaths = chain(walk('content', { directories: false }))
+          .uniq()
+          .value()
 
-      const nonEnglishPaths = chain(Object.values(libLanguages))
-        .filter((language) => language.code !== 'en')
-        .map((language) => walk(`${language.dir}/content`, { directories: false }))
-        .flatten()
-        .uniq()
-        .value()
+        const nonEnglishPaths = chain(Object.values(libLanguages))
+          .filter((language) => language.code !== 'en')
+          .map((language) => walk(`${language.dir}/content`, { directories: false }))
+          .flatten()
+          .uniq()
+          .value()
 
-      const diff = difference(nonEnglishPaths, englishPaths)
-      const failureMessage = `
+        const diff = difference(nonEnglishPaths, englishPaths)
+        const failureMessage = `
 Found ${diff.length} non-English pages without a matching English page:\n - ${diff.join('\n - ')}
 
 Remove them with script/i18n/prune-stale-files.js and commit your changes using "git commit --no-verify".
 `
-      expect(diff.length, failureMessage).toBe(0)
-    })
+        expect(diff.length, failureMessage).toBe(0)
+      }
+    )
   })
 
   describe('loadPageMap', () => {
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index ee8ce51bf9..664c43aab5 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
-product: '{% ifversion fpt %}{% data reusables.gated-features.user-repo-collaborators %}{% endif %}'
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0480cd1ad4..3be45c2a1b 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -9,7 +9,6 @@ redirect_from:
   - /articles/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
-product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -22,6 +21,10 @@ shortTitle: Eliminarte a ti mismo
 ---
 
 {% data reusables.user_settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 2. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
 3. Junto al repositorio que quieres abandonar, haz clic en **Leave** (Abandonar). ![Botón Leave (Abandonar)](/assets/images/help/repository/repo-leave.png)
 4. Lee la advertencia con atención, luego haz clic en "I understand, leave this repository" (Comprendo, abandonar este repositorio). ![Cuadro de diálogo con advertencia sobre el abandono](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
index 84a44177eb..52f5555fdc 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -13,12 +13,12 @@ shortTitle: Integrar a Jira con los proyectos
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
-3. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_oauth_apps %}**. ![pestaña {% data variables.product.prodname_oauth_apps %} en la barra lateral izquierda](/assets/images/help/settings/developer-settings-oauth-apps.png)
-3. Haz clic en **Register a new application** (Registrar una aplicación nueva).
-4. En **Application name** (Nombre de la aplicación), escribe "Jira".
-5. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira.
-6. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira.
-7. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png)
+{% data reusables.user-settings.oauth_apps %}
+1. Haz clic en **Register a new application** (Registrar una aplicación nueva).
+2. En **Application name** (Nombre de la aplicación), escribe "Jira".
+3. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira.
+4. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira.
+5. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png)
 8. En **Developer applications** (Aplicaciones del programador), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index f57df57ad7..a4c3ff7d6e 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,7 +14,6 @@ shortTitle: Managing your tab size
 If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings.
 
 {% data reusables.user_settings.access_settings %}
-1. In the user settings sidebar, click **Appearance**.
-   !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 2. Under "Tab size preference", select the drop-down menu and choose your preference.
    ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png )
diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 5c8d899914..2eaa836207 100644
--- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
 
 ## Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %}
 
-Las acciones Docker y JavaScript requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos del archivo de metadatos definen las entradas, las salidas y el punto de entrada principal para tu acción.
+All actions require a metadata file. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
 
 Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 95e05bb95c..2910096e3c 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -218,6 +218,10 @@ For example:
 curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
 ```
 
+### Adding permissions settings
+
+{% data reusables.actions.oidc-permissions-token %}
+
 ## Updating your workflows for OIDC
 
 You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index c3835e7b73..e1c0cdcf16 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -56,14 +56,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 80231b121a..5f599d3228 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -50,14 +50,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index d9167ef9eb..609917b309 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring OpenID Connect in cloud providers
+title: Configurar OpenID Connect en los proveedores de servicios en la nube
 shortTitle: Configurar OpenID Connect en los proveedores de servicios en la nube
 intro: Use OpenID Connect within your workflows to authenticate with cloud providers.
 miniTocMaxHeadingLevel: 3
@@ -30,21 +30,14 @@ To use OIDC, you will first need to configure your cloud provider to trust {% da
 ## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
+1. Agregar ajustes de permisos para el token.
 2. Use the official action from your cloud provider to exchange the OIDC token (JWT) for a cloud access token.
 
 If your cloud provider doesn't yet offer an official action, you can update your workflows to perform these steps manually.
 
-### Adding permissions settings
+### Agregar ajustes de permisos
 
-El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Using official actions
 
@@ -64,7 +57,7 @@ To update your workflows using this approach, you will need to make three change
 
 ### Requesting the JWT using the Actions core toolkit
 
-The following example demonstrates how to use `actions/github-script` with the `core` toolkit to request the JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. For more information, see "[Adding actions toolkit packages](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)."
+The following example demonstrates how to use `actions/github-script` with the `core` toolkit to request the JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. Para obtener más información, consulta la sección "[Agregar paquetes de kit de herramientas de acciones](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)".
 
 ```yaml
 jobs:
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index 58ae87501b..a2f9ef9387 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring OpenID Connect in Google Cloud Platform
+title: Configurar OpenID Connect en Google Cloud Platform
 shortTitle: Configurar OpenID Connect en Google Cloud Platform
 intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.
 miniTocMaxHeadingLevel: 3
@@ -49,14 +49,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Agregar ajustes de permisos
 
-El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index e0af6a08e6..f2fbf2f407 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -54,14 +54,7 @@ This example demonstrates how to use OIDC with the official action to request a
 
 ### Agregar ajustes de permisos
 
-El flujo de trabajo requerirá una configuración de `permissions` con un valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. Si solo necesitas recuperar un token de OIDC para un solo job, entonces este permiso puede configurarse dentro de dicho job. Por ejemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md
index 7be82db638..f36b2eb91a 100644
--- a/translations/es-ES/content/actions/index.md
+++ b/translations/es-ES/content/actions/index.md
@@ -32,7 +32,6 @@ featuredLinks:
     - title: "GitHub Actions in action – Karan MV"
       href: 'https://www.youtube-nocookie.com/embed/4SWO0Pc76CU'
   videosHeading: GitHub Universe 2021 videos
-examples_source: data/product-examples/actions/code-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
 redirect_from:
   - /articles/automating-your-workflow-with-github-actions
diff --git a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index a0673d1757..cf6dccd4ef 100644
--- a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -18,16 +18,23 @@ shortTitle: Límites & facturación de los flujos de trabajo
 
 ## Acerca de la facturación para {% data variables.product.prodname_actions %}
 
+{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% else %}
-El uso de GitHub Actions es gratuito para los {% data variables.product.prodname_ghe_server %} que utilicen ejecutores auto-hospedados.
+GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 {% endif %}
 
+
+{% ifversion fpt or ghec %}
+
 ## Disponibilidad
 
 {% data variables.product.prodname_actions %} está disponible en todos los productos de {% data variables.product.prodname_dotcom %}, pero {% data variables.product.prodname_actions %} no está disponible para los repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data reusables.gated-features.more-info %}
 
+{% endif %}
+
 ## Límites de uso
 
 {% ifversion fpt or ghec %}
diff --git a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
index 4adb4d82c5..b86900fd20 100644
--- a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
@@ -90,6 +90,9 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
+| pages         | read/write  | none | read |
+{%- endif %}
 | pull-requests | read/write  | none | read |
 | repository-projects | read/write | none | read |
 | security-events     | read/write | none | read |
diff --git a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
index d41cd7c7d6..7f02c06db6 100644
--- a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
@@ -354,3 +354,50 @@ Los secretos tienen un tamaño máximo de 64 KB. Para usar secretos de un tamañ
           run: cat $HOME/secrets/my_secret.json
   ```
 {% endraw %}
+
+
+## Storing Base64 binary blobs as secrets
+
+You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+
+{% note %}
+
+**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+
+{% endnote %}
+
+1. Use `base64` to encode your file into a Base64 string. Por ejemplo:
+
+   ```
+   $ base64 -i cert.der -o cert.base64
+   ```
+
+1. Create a secret that contains the Base64 string. Por ejemplo:
+
+   ```
+   $ gh secret set CERTIFICATE_BASE64 < cert.base64
+   ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
+   ```
+
+1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  Por ejemplo:
+
+   ```yaml
+   name: Retrieve Base64 secret
+   on:
+     push:
+       branches: [ octo-branch ]
+   jobs:
+     decode-secret:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: actions/checkout@v2
+         - name: Retrieve the secret and decode it to a file
+           env:
+             {% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
+           run: |
+             echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
+         - name: Show certificate information
+           run: |
+             openssl x509 -in cert.der -inform DER -text -noout
+   ```
+
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index fc1948522f..2d62328779 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -973,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.<push>
 | `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`<br/><br/>`every/tag` |
 | `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature` |
 | `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`<br/><br/>`v2.0.0` |
+| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2. | `v1.10.1`<br/><br/>`v2.0.0` |
 
 ### Patterns to match file paths
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
index 03c6fa7067..68e25db7fd 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -38,6 +38,8 @@ Puedes generar una solicitud de firma de certificados (CSR) para tu instancia us
 
 ## Cargar un certificado TLS personalizado
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
@@ -67,6 +69,8 @@ También puedes usar la utilidad de la línea de comando `ghe-ssl-acme` en {% da
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index bc5fe2d7bd..f48c405316 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -137,5 +137,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 Puedes utilizar estas otras opciones con el comando `ghe-restore`:
-- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. Para obtener más información, consulta la sección "Utilizar una copia de seguridad y restablecer los comandos" de [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - La marca `-s` te permite seleccionar otra instantánea de copias de seguridad.
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index 8169ac363f..30a36eabbf 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -74,7 +74,7 @@ Los propietarios de las empresas pueden configurar los correos electrónicos par
 
 4. Si el correo electrónico de prueba falla, [soluciona los problemas de los parámetros de tu correo electrónico](#troubleshooting-email-delivery).
 5. Cuando el correo electrónico de prueba es exitoso, en la parte inferior de la página, haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/enterprise/management-console/save-settings.png)
-6. Espera que se complete la fase de configuración. ![Configurar tu instancia](/assets/images/enterprise/management-console/configuration-run.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 ## Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes
 
diff --git a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index eeae6fb8a8..be6dc809eb 100644
--- a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -52,9 +52,11 @@ If you use Docker container actions or service containers in your workflows, you
 
 If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
 
-## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname
+## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
 
-If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
 
 You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures:
 
diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index d11a20252e..5834c77409 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -15,8 +15,6 @@ redirect_from:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
-
 ## Acerca del inicio de sesión único de SAML para las cuentas empresariales
 
 {% data reusables.saml.dotcom-saml-explanation %}{% data reusables.saml.about-saml-enterprise-accounts %}
diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md
index cdef92694f..e4c305c6fa 100644
--- a/translations/es-ES/content/admin/index.md
+++ b/translations/es-ES/content/admin/index.md
@@ -97,12 +97,14 @@ featuredLinks:
     - '{% ifversion ghes %}/admin/installation{% endif %}'
     - '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
     - '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
     - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
     - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
+    - /admin/configuration/configuring-github-connect/managing-github-connect
     - /admin/enterprise-support/about-github-enterprise-support
   videos:
     - title: GitHub in the Enterprise – Maya Ross
diff --git a/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
new file mode 100644
index 0000000000..12ca45f88c
--- /dev/null
+++ b/translations/es-ES/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your enterprise
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Enterprise owners can access compliance reports for the enterprise.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Leer más
+
+- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
diff --git a/translations/es-ES/content/admin/overview/index.md b/translations/es-ES/content/admin/overview/index.md
index f947bc951e..7693b0c3b4 100644
--- a/translations/es-ES/content/admin/overview/index.md
+++ b/translations/es-ES/content/admin/overview/index.md
@@ -15,5 +15,6 @@ children:
   - /system-overview
   - /about-the-github-enterprise-api
   - /creating-an-enterprise-account
+  - /accessing-compliance-reports-for-your-enterprise
 ---
 For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 848d68d68f..949c933e99 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -149,9 +149,8 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
 {% data reusables.organizations.delete-ssh-ca %}
 
 {% ifversion ghec or ghae %}
-
 ## Further reading
 
-- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
-
+- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
 {% endif %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 5076cf7d6b..a686a2dfa1 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -81,27 +81,23 @@ Las siguientes variables siempre están disponibles en el ambiente de gancho de
 
 La variable `$GITHUB_VIA` se encuentra disponible en el ambiente de gancho de pre-recepción cuando la actualización de la referencia que activa el gancho ocurre a través ya sea de la interface web o de la API para {% data variables.product.prodname_ghe_server %}. El valor describe la acción que actualizó la referencia.
 
-| Valor                      | Acción                                                                                                                                                                                     | Más información                                                                                                                                                                             |
-|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <pre>auto-merge deployment api</pre>  | Fusión automática de la rama base a través del despliegue que se creó con la API                                                                                                           | "[Crear un despliegue](/rest/reference/deployments#create-a-deployment)" en la documentación de la API de REST                                                                              |
-| <pre>blob#save</pre> | Cambio al contenido de un archivo en la interface web                                                                                                                                      | "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                                          |
-| <pre>branch merge api</pre> | Fusión de una rama a través de la API                                                                                                                                                      | "[Fusionar una rama](/rest/reference/branches#merge-a-branch)" en la documentación de la API de REST                                                                                        |
-| <pre>branches page delete button</pre> | Borrado de una rama en la interface web                                                                                                                                                    | "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)"              |
-| <pre>git refs create api</pre> | Creación de una referencia a través de la API                                                                                                                                              | "[Base de datos de Git](/rest/reference/git#create-a-reference)" en la documentación de la API de REST                                                                                      |
-| <pre>git refs delete api</pre> | Borrado de una referencia a través de la API                                                                                                                                               | "[Bases de datos de Git](/rest/reference/git#delete-a-reference)" En la documentación de la API de REST                                                                                     |
-| <pre>git refs update api</pre> | Actualización de una referencia a tracvés de la API                                                                                                                                        | "[Base de datos de Git](/rest/reference/git#update-a-reference)" en la documentación de la API de REST                                                                                      |
-| <pre>git repo contents api</pre> | Cambio al contenido de un archivo a través de la API                                                                                                                                       | "[Crear o actualizar el contenido de un archivo](/rest/reference/repos#create-or-update-file-contents)" en la API de REST                                                                   |
-| <pre>merge base into head</pre> | Actualiza la rama de tema de la rama base cuando la rama base requiere verificaciones de estado estrictas (a través de **Actualización de rama** en una solicitud de cambios, por ejemplo) | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)"                                                        |
-| <pre>pull request branch delete button</pre> | Borrado de una rama de tema desde una solicitud de cambios en la interface web                                                                                                             | "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
-| <pre>pull request branch undo button</pre> | Restablecimiento de una rama de tema desde una solicitud de cambios en la interface web                                                                                                    | "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)"                |
-| <pre>pull request merge api</pre> | Fusión de una solicitud de cambios a través de la API                                                                                                                                      | "[Cambios](/rest/reference/pulls#merge-a-pull-request)" en la documentación de la API de REST                                                                                               |
-| <pre>pull request merge button</pre> | Fusión de una solicitud de cambios en la interface web                                                                                                                                     | "[Fusionar una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)"                                       |
-| <pre>pull request revert button</pre> | Revertir una solicitud de cambios                                                                                                                                                          | "[Revertir una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)"                                                                      |
-| <pre>releases delete button</pre> | Borrado de una solicitud                                                                                                                                                                   | "[Administrar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)"                                                 |
-| <pre>stafftools branch restore</pre> | Restablecimiento de una rama desde el panel de administrador del sitio                                                                                                                     | "[Panel de administrador del sitio](/admin/configuration/site-admin-dashboard#repositories)"                                                                                                |
-| <pre>tag create api</pre> | Creación de una etiqueta a través de la API                                                                                                                                                | "[Base de datos de Git](/rest/reference/git#create-a-tag-object)" en la documentación de la API de REST                                                                                     |
-| <pre>slumlord (#<em>SHA</em>)</pre> | Confirmar a través de Subversion                                                                                                                                                           | "[Compatibilidad para los clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)"                                   |
-| <pre>web branch create</pre> | Creación de una rama a través de la interface web                                                                                                                                          | "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)"              |
+| Valor                      | Acción                                                                           | Más información                                                                                                                                                                |
+|:-------------------------- |:-------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <pre>auto-merge deployment api</pre>  | Fusión automática de la rama base a través del despliegue que se creó con la API | "[Crear un despliegue](/rest/reference/deployments#create-a-deployment)" en la documentación de la API de REST                                                                 |
+| <pre>blob#save</pre> | Cambio al contenido de un archivo en la interface web                            | "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                             |
+| <pre>branch merge api</pre> | Fusión de una rama a través de la API                                            | "[Fusionar una rama](/rest/reference/branches#merge-a-branch)" en la documentación de la API de REST                                                                           |
+| <pre>branches page delete button</pre> | Borrado de una rama en la interface web                                          | "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" |
+| <pre>git refs create api</pre> | Creación de una referencia a través de la API                                    | "[Base de datos de Git](/rest/reference/git#create-a-reference)" en la documentación de la API de REST                                                                         |
+| <pre>git refs delete api</pre> | Borrado de una referencia a través de la API                                     | "[Bases de datos de Git](/rest/reference/git#delete-a-reference)" En la documentación de la API de REST                                                                        |
+| <pre>git refs update api</pre> | Actualización de una referencia a tracvés de la API                              | "[Base de datos de Git](/rest/reference/git#update-a-reference)" en la documentación de la API de REST                                                                         |
+| <pre>git repo contents api</pre> | Cambio al contenido de un archivo a través de la API                             | "[Crear o actualizar el contenido de un archivo](/rest/reference/repos#create-or-update-file-contents)" en la API de REST                                                      |
+
+{%- ifversion ghes > 3.0 %}
+| 
+
+`merge` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
+| <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | | <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | | <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | | <pre>pull request merge api</pre> | Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | | <pre>pull request merge button</pre> | Merge of a pull request in the web interface | "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | | <pre>pull request revert button</pre> | Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | | <pre>releases delete button</pre> | Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | | <pre>stafftools branch restore</pre> | Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | | <pre>tag create api</pre> | Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | | <pre>slumlord (#<em>SHA</em>)</pre> | Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | | <pre>web branch create</pre> | Creation of a branch via the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" |
 
 #### Disponible para las fusiones de solicitudes de cambio
 
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index 1ba3f5b7f9..f4bc85a82d 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -9,6 +9,7 @@ redirect_from:
 intro: 'Una vez que se ha creado un equipo, los administradores de la organización pueden agregar usuarios desde {% data variables.product.product_location %} al equipo y determinar a qué repositorios tienen acceso.'
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -30,8 +31,12 @@ Cada equipo tiene sus propios premisos de acceso definidos de manera individual
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
+{% ifversion ghes %}
+
 ## Asignar equipos a los grupos LDAP (para instancias que usan la sincronización LDAP para la autenticación de usuario)
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
 Para agregar un nuevo miembro a un equipo sincronizado con un grupo LDAP, agrega el usuario como un miembro del grupo LDAP o comunícate con el administrador LDAP.
+
+{% endif %}
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
index 22ddbae2cf..f62ddb7471 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
@@ -7,6 +7,7 @@ redirect_from:
   - /admin/user-management/continuous-integration-using-jenkins
 versions:
   ghes: '*'
+  ghae: '*'
 type: reference
 topics:
   - CI
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
index 52334965f2..e638566bb1 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/creating-teams
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -32,6 +33,8 @@ A prudent combination of teams is a powerful way to control repository access. F
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
 
+{% ifversion ghes %}
+
 ## Creating teams with LDAP Sync enabled
 
 Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
@@ -60,3 +63,5 @@ You must be a site admin and an organization owner to create a team with LDAP sy
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 5e03f8fdc4..9c0da676b8 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
 title: Administrar proyectos utilizando Jira
-intro: 'Puedes integrar Jura con {% data variables.product.prodname_enterprise %} para la administración de proyectos.'
+intro: 'Puedes integrar Jura con {% data variables.product.product_name %} para la administración de proyectos.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira
   - /enterprise/admin/articles/project-management-using-jira
@@ -10,6 +10,7 @@ redirect_from:
   - /admin/user-management/managing-projects-using-jira
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
index b7e75cd92b..6293dbd233 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/removing-users-from-teams-and-organizations
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -25,6 +26,8 @@ Solo los propietarios o los administradores del equipo pueden eliminar miembros
 
 ## Eliminar un miembro del equipo
 
+{% ifversion ghes %}
+
 {% warning %}
 
 **Nota:** {% data reusables.enterprise_management_console.badge_indicator %}
@@ -33,6 +36,8 @@ Para eliminar un miembro existente de un equipo sincronizado a un grupo LDAP, co
 
 {% endwarning %}
 
+{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 09b2bb8c4b..db5d0f0baf 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -8,6 +8,7 @@ redirect_from:
   - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
   - /github/authenticating-to-github/creating-a-personal-access-token
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
+  - /github/extending-github/git-automation-with-oauth-tokens
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 2fb4b73679..4b55fc72f2 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,11 @@ shortTitle: Llaves de implementación
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
 3. En la barra lateral izquierda, haz clic en **Deploy keys** (Llaves de implementación). ![Parámetro de llaves de implementación](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
 4. En la página de Llaves de implementación, anota las llaves de implementación asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay llaves de implementación válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de llaves de implementación](/assets/images/help/settings/settings-deploy-key-review.png)
 
 Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)".
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
new file mode 100644
index 0000000000..2e6daf26d3
--- /dev/null
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
@@ -0,0 +1,119 @@
+---
+title: About code scanning alerts
+intro: 'Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About alerts from {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+## About alert details
+
+Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
+
+If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+
+When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+
+### About severity levels
+
+Alert severity levels may be `Error`, `Warning`, or `Note`.
+
+If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+### About security severity levels
+
+{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
+
+To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
+
+By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+### About labels for alerts that are not found in application code
+
+{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
+
+- **Generated**: Code generated by the build process
+- **Test**: Test code
+- **Library**: Library or third-party code
+- **Documentation**: Documentation
+
+{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
+
+Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
+
+![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
+
+On the alert page, you can see that the filepath is marked as library code (`Library` label).
+
+![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
+
+{% if codeql-ml-queries %}
+
+## About experimental alerts
+
+{% data reusables.code-scanning.beta-codeql-ml-queries %}
+
+In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
+
+![Code scanning experimental alert in list](/assets/images/help/repository/code-scanning-experimental-alert-list.png)
+
+### Benefits of using machine learning models to extend queries
+
+Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
+
+Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
+
+{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
+
+### Alerts identified using machine learning
+
+Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
+
+![Code scanning experimental alert details](/assets/images/help/repository/code-scanning-experimental-alert-show.png)
+
+## Enabling experimental alerts
+
+The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you update your workflow to run an additional query suite this will increase the analysis time.
+
+``` yaml
+- uses: github/codeql-action/init@v1
+  with:
+    # Run extended queries including queries using machine learning
+    queries: security-extended
+```
+
+For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+## Disabling experimental alerts
+
+The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
+
+- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
+- Specify details of the repositories or organizations that are affected
+- Request an escalation to engineering
+
+{% endif %}
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index fb05626d65..70303ae4d7 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -43,7 +43,7 @@ There are two main ways to use {% data variables.product.prodname_codeql %} anal
 
 ## About {% data variables.product.prodname_codeql %} queries
 
-{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://codeql.github.com/) on the {% data variables.product.prodname_codeql %} website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
 
 You can run additional queries as part of your code scanning analysis. 
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index fa6d5e121a..7d22ab101e 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -18,7 +18,6 @@ topics:
   - Code scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index eafbc64c0b..af256d5d03 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -24,7 +24,7 @@ topics:
   - Python
 shortTitle: Configure code scanning
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
@@ -89,7 +89,7 @@ If you scan pull requests, then the results appear as alerts in a pull request c
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ### Defining the severities causing pull request check failure
 
-By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)."
+By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -351,7 +351,7 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 
 You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 {% if codeql-packs %}
 ### Working with custom configuration files
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 42c5f3df55..6dc4d24289 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -26,7 +26,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 622a6eb37f..6c1d00f0ab 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -16,6 +16,7 @@ topics:
   - Code scanning
 children:
   - /about-code-scanning
+  - /about-code-scanning-alerts
   - /triaging-code-scanning-alerts-in-pull-requests
   - /setting-up-code-scanning-for-a-repository
   - /managing-code-scanning-alerts-for-your-repository
@@ -28,4 +29,4 @@ children:
   - /running-codeql-code-scanning-in-a-container
   - /viewing-code-scanning-logs
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index bc07386975..7747b61120 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -23,62 +23,9 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
-## About alerts from {% data variables.product.prodname_code_scanning %}
-
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
-
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-
-{% data reusables.code-scanning.upload-sarif-alert-limit %}
-
-## About alerts details
-
-Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
-
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
-
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
-
-When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
-
-### About severity levels
-
-Alert severity levels may be `Error`, `Warning`, or `Note`.
-
-By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### About security severity levels
-
-{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
-
-To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
-
-By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-### About labels for alerts that are not found in application code
-
-{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
-
-- **Generated**: Code generated by the build process
-- **Test**: Test code
-- **Library**: Library or third-party code
-- **Documentation**: Documentation
-
-{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
-
-Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code.
-
-![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
-
-On the alert page, you can see that the filepath is marked as library code (`Library` label).
-
-![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
-
 ## Viewing the alerts for a repository
 
 Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
@@ -104,6 +51,8 @@ By default, the code scanning alerts page is filtered to show alerts for the def
 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
    ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
 
+For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
+
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
 
@@ -133,7 +82,7 @@ If you enter multiple filters, the view will show alerts matching _all_ these fi
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 
-You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
+You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
 
 {% endif %}
 
@@ -177,7 +126,7 @@ You can search the list of alerts. This is useful if there is a large number of
 
 {% endif %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index 3f26780980..1de9bb7212 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -23,7 +23,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index c1ea916c94..ca23913fcb 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -5,9 +5,7 @@ intro: You can add code scanning alerts to issues using task lists. This makes i
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
-  fpt: '*'
-  ghes: '> 3.3'
-  ghae: issue-5036
+  feature: 'code-scanning-task-lists'
 type: how_to
 topics:
   - Advanced Security
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 8b4a6464af..66ae7d484f 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -21,7 +21,7 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 8468cef2c5..75da441f12 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -27,7 +27,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
@@ -191,6 +190,19 @@ Si divides tu análisis en varios flujos de trabajo como se describió anteriorm
 
 Si tu análisis aún es muy lento como para ejecutarse durante eventos de `push` o de `pull_request`, entonces tal vez quieras activar el análisis únicamente en el evento de `schedule`. Para obtener más información, consulta la sección "[Eventos](/actions/learn-github-actions/introduction-to-github-actions#events)".
 
+### Check which query suites the workflow runs
+
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
+
+You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)".
+
+{% if codeql-ml-queries %}
+{% note %}
+
+**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+{% endnote %}
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ## Los resultados difieren de acuerdo con la plataforma de análisis
 
@@ -206,7 +218,7 @@ Si la ejecución de un flujo de trabajo para {% data variables.product.prodname_
 
 ## Error: "Out of disk" o "Out of memory"
 
-En proyectos muy grandes, el {% data variables.product.prodname_codeql %} podría quedarse sin memoria o sin espacio de almacenamiento en el ejecutor.
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
 {% ifversion fpt or ghec %}Si te encuentras con este problema en un ejecutor de {% data variables.product.prodname_actions %}, contacta a {% data variables.contact.contact_support %} para que podamos investigar el problema.
 {% else %}Si llegas a tener este problema, intenta incrementar la memoria en el ejecutor.{% endif %}
 
diff --git a/translations/es-ES/content/code-security/code-scanning/index.md b/translations/es-ES/content/code-security/code-scanning/index.md
index 4b9e446478..748d684738 100644
--- a/translations/es-ES/content/code-security/code-scanning/index.md
+++ b/translations/es-ES/content/code-security/code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /using-codeql-code-scanning-with-your-existing-ci-system
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
index 0a120a5059..d1f394b381 100644
--- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -19,7 +19,7 @@ topics:
   - Webhooks
   - Integration
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md
index 8a4cf7e9c0..d283a0732c 100644
--- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md
+++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md
@@ -21,4 +21,4 @@ children:
   - /uploading-a-sarif-file-to-github
   - /sarif-support-for-code-scanning
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index ab3879863f..c1fc8e6166 100644
--- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -21,7 +21,7 @@ topics:
   - Integration
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index c0b9b3afea..0beaf40ec0 100644
--- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -24,7 +24,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index 7c42e31833..6105ca77b6 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -28,7 +28,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
@@ -83,7 +83,7 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
 
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index 35ceb491ff..19c553cb72 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -28,4 +28,3 @@ children:
   - /migrating-from-the-codeql-runner-to-codeql-cli
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index 441e52b87a..74078a9855 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -25,7 +25,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
index accdd7ebbb..13bf915705 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -23,7 +23,7 @@ topics:
   - Integration
   - CI
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
index 92361d61a2..25412c70df 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
@@ -139,3 +139,9 @@ You can view and manage alerts from security features to address dependencies an
 
 {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
+
+{% ifversion ghec %}
+## Further reading
+
+"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/content/code-security/guides.md b/translations/es-ES/content/code-security/guides.md
index 0c1e740b57..f79b1c7b9e 100644
--- a/translations/es-ES/content/code-security/guides.md
+++ b/translations/es-ES/content/code-security/guides.md
@@ -30,6 +30,7 @@ includeGuides:
   - /code-security/secret-scanning/secret-scanning-partners
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index efa692621b..7751ec144d 100644
--- a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,6 +27,6 @@ También puedes bloquear usuarios. Para obtener más información, consulta la s
 ## Limitar las interacciones para tu cuenta de usuario
 
 {% data reusables.user_settings.access_settings %}
-1. En tu barra lateral de configuración de usuario, debajo de "Configuración de moderación", da clic en **Límites de interacción**. ![Pestaña de "límites de interacción" en la barra lateral de la configuración de usuario](/assets/images/help/settings/settings-sidebar-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![Opciones de límites de interacción temporarios](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index 6c3a6932c0..a9084bef8f 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -40,7 +40,7 @@ You can set the following top-level keys for each issue form.
 | `description` | A description for the issue form template, which appears in the template chooser interface. | Required | String |
 | `body` | Definition of the input types in the form. | Required | Array |
 | `assignees` | People who will be automatically assigned to issues created with this template. | Optional | Array or comma-delimited string |
-| `labels` | Labels that will automatically be added to issues created with this template. | Optional | String |
+| `labels` | Labels that will automatically be added to issues created with this template. | Optional | Array or comma-delimited string |
 | `title` | A default title that will be pre-populated in the issue submission form. | Optional | String |
 
 For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)."
diff --git a/translations/es-ES/content/developers/overview/about-githubs-apis.md b/translations/es-ES/content/developers/overview/about-githubs-apis.md
index d21ed9a51e..03d3673697 100644
--- a/translations/es-ES/content/developers/overview/about-githubs-apis.md
+++ b/translations/es-ES/content/developers/overview/about-githubs-apis.md
@@ -3,6 +3,8 @@ title: Acerca de las API de GitHub
 intro: 'Aprende sobre las API de {% data variables.product.prodname_dotcom %} para extender y personalizar tu experiencia en {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /v3/versions
+  - /articles/getting-started-with-the-api
+  - /github/extending-github/getting-started-with-the-api
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/developers/overview/managing-deploy-keys.md b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
index f96d01a780..a0c48a6bdd 100644
--- a/translations/es-ES/content/developers/overview/managing-deploy-keys.md
+++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
@@ -34,11 +34,11 @@ En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente
 #### Configuración
 
 1. Habilita el reenvío de agente localmente. Consulta [nuestra guía sobre el redireccionamiento del agente SSH][ssh-agent-forwarding] para obtener más información.
-2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, el habilitar el reenvío de agentes en un script de bash se vería más o menos así: `ssh -A serverA 'bash -s' < deploy.sh`
+2. Configura tus scripts de despliegue para utilizar el reenvío de agente. For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh`
 
 ## Clonado de HTTPS con tokens de OAuth
 
-Si no quieres utilizar llaves SSH, puedes utilizar [HTTPS con tokens de OAuth][git-automation].
+If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
 
 #### Pros
 
@@ -57,7 +57,7 @@ Si no quieres utilizar llaves SSH, puedes utilizar [HTTPS con tokens de OAuth][g
 
 #### Configuración
 
-Consulta [nuestra guía sobre la automatización de tokens en Git][git-automation].
+See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
 ## Llaves de implementación
 
@@ -184,9 +184,6 @@ Esto significa que no puedes automatizar la creación de las cuentas. Pero si qu
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
-[git-automation]: /articles/git-automation-with-oauth-tokens
-[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
-
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
new file mode 100644
index 0000000000..fef163b17b
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
@@ -0,0 +1,35 @@
+---
+title: About GitHub Marketplace
+intro: '{% data variables.product.prodname_marketplace %} contains tools that add functionality and improve your workflow.'
+redirect_from:
+  - /articles/about-github-marketplace
+  - /github/customizing-your-github-workflow/about-github-marketplace
+  - /github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace  
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
+
+If you purchase a paid tool, you'll pay for your tool subscription with the same billing information you use to pay for your {% data variables.product.product_name %} subscription, and receive one bill on your regular billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+You may also have the option to select a free 14-day trial on some tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+## Finding tools on {% data variables.product.prodname_marketplace %}
+
+You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)."
+
+{% data reusables.actions.actions-not-verified %}
+
+Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)."
+
+## Building and listing a tool on {% data variables.product.prodname_marketplace %}
+
+For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)."
+
+## Further reading
+
+- "[Purchasing and installing apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)"
+- "[Managing billing for {% data variables.product.prodname_marketplace %} apps](/articles/managing-billing-for-github-marketplace-apps)"
+- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)"
+- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)"
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
new file mode 100644
index 0000000000..7748a24e47
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -0,0 +1,43 @@
+---
+title: Acerca de las integraciones
+intro: 'Las integraciones son herramientas y servicios que se conectan con {% data variables.product.product_name %} para complementar y extender tu flujo de trabajo.'
+redirect_from:
+  - /articles/about-integrations
+  - /github/customizing-your-github-workflow/about-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/about-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. También puedes instalar {% data variables.product.prodname_github_apps %} de un tercero en un repositorio específico donde tengas permisos de administrador o que sea propiedad de tu organización.
+
+## Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}
+
+Las integraciones pueden ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} o cualquiera que utilice las API o webhooks de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
+
+Las {% data variables.product.prodname_github_apps %} ofrecen permisos granulares y solicitan acceso únicamente a lo que necesita la app. Las {% data variables.product.prodname_github_apps %} también ofrecen un permiso a nivel de usuario que cada uno de estos debe autorizar individualmente cuando se instala la app o cuando el integrador cambia los permisos que solicita la app.
+
+Para obtener más información, consulta:
+- "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
+- "[Acerca de las apps](/apps/about-apps/)"
+- "[Permisos a nivel de usario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
+- "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Autorizar las {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations/)"
+
+Puedes instalar una {% data variables.product.prodname_github_app %} preconfigurada, si los integradores o los creadores de la aplicación han creado su aplicación con el flujo de manifiesto de {% data variables.product.prodname_github_app %}. Para obtener más información sobre cómo ejecutar tu {% data variables.product.prodname_github_app %} con configuración automatizada, comunícate con el integrador o el creador de la aplicación.
+
+Puedes crear una {% data variables.product.prodname_github_app %} con configuración simplificada si creas tu aplicación con Probot. Para obtener más información, consulta el sitio [Documentos de Probot](https://probot.github.io/docs/).
+
+## Descubrir integraciones en {% data variables.product.prodname_marketplace %}
+
+Puedes encontrar una integración para instalar o publicar tu propia integración en {% data variables.product.prodname_marketplace %}.
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contiene a las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)".
+
+## Integraciones compradas directamente a los integradores
+
+También puedes comprar algunas integraciones directamente a los integradores. Como miembro de una organización, si encuentras una {% data variables.product.prodname_github_app %} que te gustaría usar, puedes solicitar que una organización apruebe o instale la aplicación para la organización.
+
+Si tienes permisos de administrador para todos los repositorios que son propiedad de una organización en la que la aplicación está instalada, puedes instalar las {% data variables.product.prodname_github_apps %} con los permisos de nivel de repositorio sin tener que solicitar al propietario de la organización que apruebe la aplicación. Cuando un integrador cambia los permisos de la aplicación, si los permisos son solo para un repositorio, los propietarios de la organización y las personas con permisos de administrador para un repositorio con esa aplicación instalada pueden revisar y aceptar los nuevos permisos.
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
new file mode 100644
index 0000000000..8c23c86ea4
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
@@ -0,0 +1,32 @@
+---
+title: Acerca de webhooks
+redirect_from:
+  - /post-receive-hooks
+  - /articles/post-receive-hooks
+  - /articles/creating-webhooks
+  - /articles/about-webhooks
+  - /github/extending-github/about-webhooks
+intro: Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% tip %}
+
+**Sugerencia:**{% data reusables.organizations.owners-and-admins-can %} administrar webhooks para una organización. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+Los webhooks se pueden disparar siempre que se realicen una variedad de acciones en un repositorio o una organización. Por ejemplo, puedes configurar tus webhooks para ejecutarse siemrpe que:
+
+* Se suba a un repositorio.
+* Se abra una solicitud de extracción.
+* Se cree un sitio {% data variables.product.prodname_pages %}.
+* Se agregue un nuevo miembro a un equipo.
+
+Al utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, puedes hacer que estos webhooks actualicen un rastreador de propuesta externo, activen compilaciones de IC, actualicen una réplica de respaldo o incluso desplieguen en tu servidor de producción.
+
+Para configurar un webhook nuevo, necesitarás acceso a un servidor externo y estar familiarizado con los procedimientos técnicos involucrados. Para obtener ayuda para crear un webhook, lo cual incluye un listado completo de las acciones con las que lo puedes asociar, consulta la secicón "[Webhooks](/webhooks)".
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
new file mode 100644
index 0000000000..cd5871557a
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -0,0 +1,55 @@
+---
+title: Extensiones e integraciones de GitHub
+intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.'
+redirect_from:
+  - /articles/about-github-extensions-for-third-party-applications
+  - /articles/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Extensiones & integraciones
+---
+
+## Herramientas del editor
+
+Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y Visual Studio.
+
+### {% data variables.product.product_name %} para Atom
+
+Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para obtener más información, consulta el [{% data variables.product.product_name %} oficial para el sitio de Atom](https://github.atom.io/).
+
+### {% data variables.product.product_name %} para Unity
+
+Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs).
+
+### {% data variables.product.product_name %} para Visual Studio
+
+Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs).
+
+### {% data variables.product.prodname_dotcom %} para Visual Studio Code
+
+Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github).
+
+## Herramientas de gestión de proyectos
+
+Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de administración de proyectos de terceros, tales como Jira.
+
+### Integración de Jira Cloud y {% data variables.product.product_name %}.com
+
+Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. Para obtener más información, visita la [App de integración de Jira](https://github.com/marketplace/jira-software-github) en marketplace.
+
+## Herramientas de comunicación para equipos
+
+Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de comunicación de equipos de terceros, tales como Slack o Microsoft Teams.
+
+### Integración con Slack y con {% data variables.product.product_name %}
+
+Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, lanzamientos, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack.
+
+The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace.
+
+### Microsoft Teams y su integración con {% data variables.product.product_name %}
+
+Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambios, confirmaciones, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource.
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
new file mode 100644
index 0000000000..7c954db5a8
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
@@ -0,0 +1,20 @@
+---
+title: Explorar integraciones
+intro: |-
+  Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y
+   servicios diseñados por la comunidad de {% data variables.product.product_name %}.
+redirect_from:
+  - /articles/exploring-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-integrations
+  - /about-webhooks
+  - /about-github-marketplace
+  - /github-extensions-and-integrations
+---
+
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md
new file mode 100644
index 0000000000..508c9c5dda
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md
@@ -0,0 +1,17 @@
+---
+title: Personalizar tu flujo de trabajo de GitHub
+intro: 'Learn how you can customize your {% data variables.product.prodname_dotcom %} workflow with extensions, integrations, {% data variables.product.prodname_marketplace %}, and webhooks.'
+redirect_from:
+  - /categories/customizing-your-github-workflow
+  - /github/customizing-your-github-workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: '*'
+  ghes: '*'
+children:
+  - /exploring-integrations
+  - /purchasing-and-installing-apps-in-github-marketplace
+shortTitle: Personaliza tu flujo de trabajo
+---
+
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
new file mode 100644
index 0000000000..d37953ecdd
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
@@ -0,0 +1,15 @@
+---
+title: Comprar e instalar aplicaciones en el Mercado GitHub
+intro: '{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Cuando encuentras una aplicación paga que desearías usar para tu cuenta personal u organización, puedes comprar e instalar la app utilizando tu información de facturación existente.'
+redirect_from:
+  - /articles/purchasing-and-installing-apps-in-github-marketplace
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /installing-an-app-in-your-personal-account
+  - /installing-an-app-in-your-organization
+shortTitle: Instalar apps de marketplace
+---
+
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
new file mode 100644
index 0000000000..5f9cc47bb2
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: Instalar una app en tu organización
+intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu organización.'
+redirect_from:
+  - /articles/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Organización de apps de instalación
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu organización usando el método de pago existente de tu organización.
+
+{% data reusables.marketplace.free-trials %}
+
+## Instalar una {% data variables.product.prodname_github_app %} en tu organización
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Si la aplicación requiere acceso a los repositorios, decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## Instalar una {% data variables.product.prodname_oauth_app %} en tu organización
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Revisa la información acerca del acceso de la app a tu cuenta personal, a tus organizaciones y a los datos, luego haz clic en **Authorize application** (Autorizar aplicación).
+
+## Leer más
+
+- "[Actualizar el método de pago de tu organización](/articles/updating-your-organization-s-payment-method)"
+- "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)"
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
new file mode 100644
index 0000000000..b18d3a2ef3
--- /dev/null
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -0,0 +1,49 @@
+---
+title: Instalar una app en tu cuenta personal
+intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu cuenta personal.'
+redirect_from:
+  - /articles/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Instalar una cuenta de usuario de la app
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu cuenta personal usando tu método de pago existente.
+
+{% data reusables.marketplace.free-trials %}
+
+## Instalar una {% data variables.product.prodname_github_app %} en tu cuenta personal
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## Instalar una {% data variables.product.prodname_oauth_app %} en tu cuenta personal
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Revisa la información acerca del acceso de la app a tu cuenta personal y a tus datos, luego haz clic en **Authorize application** (Autorizar aplicación).
+
+## Leer más
+
+- "[Actualizar el método de pago de tu cuenta personal](/articles/updating-your-personal-account-s-payment-method)"
+- "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)"
diff --git a/translations/es-ES/content/get-started/index.md b/translations/es-ES/content/get-started/index.md
index 3411ebc4c4..10bd9a88a2 100644
--- a/translations/es-ES/content/get-started/index.md
+++ b/translations/es-ES/content/get-started/index.md
@@ -62,6 +62,7 @@ children:
   - /exploring-projects-on-github
   - /getting-started-with-git
   - /using-git
+  - /customizing-your-github-workflow
   - /privacy-on-github
 ---
 
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index a4098763ca..5789072dd7 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -12,7 +12,7 @@ shortTitle: GitHub AE trial
 
 Puedes configurar un periodo de 90 días para evaluar {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
-- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
+- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the deployment of {% data variables.product.prodname_ghe_managed %}.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
 ## Configurar tu prueba de {% data variables.product.prodname_ghe_managed %}
@@ -39,24 +39,24 @@ The email address you entered above will receive instructions on how to access y
 
 {% note %}
 
-**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} instance are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
+**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} deployment are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
 
 {% endnote %}
 
 ## Navigating to your enterprise
 
-You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
+You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} deployment. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} deployments in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
 1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
 ## Pasos siguientes
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
+Once your deployment has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
 ## Finalizar tu prueba
 
-You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
+You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the deployment is automatically deleted.
 
 Si necesitas más tiempo para evaluar {% data variables.product.prodname_ghe_managed %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión.
 
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index f5c9633c79..d0491e93f6 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -25,11 +25,9 @@ shortTitle: Enterprise Cloud trial
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
-{% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
 
-{% data reusables.enterprise-accounts.emu-short-summary %}
-
-{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
 
 {% data reusables.products.which-product-to-use %}
 
@@ -39,7 +37,11 @@ You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe
 
 Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
 
-Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
 
 ## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
 
@@ -62,11 +64,13 @@ After setting up your trial, you can explore {% data variables.product.prodname_
 
 ## Finishing your trial
 
-You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
 
-If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}. 
 
-Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/translations/es-ES/content/get-started/using-github/github-command-palette.md b/translations/es-ES/content/get-started/using-github/github-command-palette.md
index 9ba9add110..bb08acddd0 100644
--- a/translations/es-ES/content/get-started/using-github/github-command-palette.md
+++ b/translations/es-ES/content/get-started/using-github/github-command-palette.md
@@ -26,10 +26,12 @@ The ability to run commands directly from your keyboard, without navigating thro
 
 ## Opening the {% data variables.product.prodname_command_palette %}
 
-Open the command palette using one of the following keyboard shortcuts:
+Open the command palette using one of the following default keyboard shortcuts:
 - Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
 - Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
+You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)."
+
 When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
 ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
@@ -42,6 +44,12 @@ When you open the command palette, it shows your location at the top left and us
 
 {% endnote %}
 
+### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
+
+
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode. 
+
+![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
 ## Navigating with the {% data variables.product.prodname_command_palette %}
 
 You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
@@ -96,7 +104,7 @@ You can use the {% data variables.product.prodname_command_palette %} to run com
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. The default keyboard shortcuts to open the command palette in command mode are <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac). If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -106,6 +114,7 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 4. Use the arrow keys to highlight the command you want and use <kbd>Enter</kbd> to run it.
 
+
 ## Closing the command palette
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
@@ -113,6 +122,8 @@ When the command palette is active, you can use one of the following keyboard sh
 - Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
 - Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.  
+
 ## {% data variables.product.prodname_command_palette %} reference
 
 ### Keystroke functions
diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
index 7ba91f622a..24f535b50c 100644
--- a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
@@ -91,7 +91,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 |<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}
 |<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
 |<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
@@ -100,6 +101,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
 |<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
 
+
 ## Issue and pull request lists
 
 | Keyboard shortcut | Description
diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md
index db12e856e3..bef795a6f8 100644
--- a/translations/es-ES/content/github/index.md
+++ b/translations/es-ES/content/github/index.md
@@ -12,8 +12,6 @@ versions:
   ghae: '*'
 children:
   - /copilot
-  - /customizing-your-github-workflow
-  - /extending-github
   - /site-policy
   - /site-policy-deprecated
 ---
diff --git a/translations/es-ES/content/issues/index.md b/translations/es-ES/content/issues/index.md
index a788404d48..14b260945c 100644
--- a/translations/es-ES/content/issues/index.md
+++ b/translations/es-ES/content/issues/index.md
@@ -33,6 +33,7 @@ featuredLinks:
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
   videosHeading: GitHub Universe 2021 videos
+product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
 layout: product-landing
 beta_product: false
 versions:
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md
index c2169827fe..637086f77e 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -76,5 +76,5 @@ Any issues that are referenced in a task list specify that they are tracked by t
 
 ## Further reading
 
-* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% if code-scanning-task-lists %}
 * "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index d4ad5f88ae..80e960d30c 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -153,7 +153,7 @@ Query parameter | Example
 `projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` creates an issue with the title "Bug fix" and adds it to the organization's project board 1.
 `template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` creates an issue with a template in the issue body. The `template` query parameter works with templates stored in an `ISSUE_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
index cb2fd4b3b9..37b52ddca9 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
@@ -1,6 +1,6 @@
 ---
 title: Mantener segura tu organización
-intro: 'Los propietarios de la organización tienen varias funciones que los ayudan a mantener seguros los proyectos y los datos. Si eres el propietario de una organización, deberás revisar frecuentemente las bitácoras de auditoría de la misma{% ifversion not ghae %}, los estados de 2FA de los miembros,{% endif %} y la configuración de las aplicaciones para garantizar que no haya ocurrido ningún tipo de actividad maliciosa o no autorizada.'
+intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -14,14 +14,8 @@ topics:
   - Organizations
   - Teams
 children:
-  - /viewing-whether-users-in-your-organization-have-2fa-enabled
-  - /preparing-to-require-two-factor-authentication-in-your-organization
-  - /requiring-two-factor-authentication-in-your-organization
-  - /managing-security-and-analysis-settings-for-your-organization
-  - /managing-allowed-ip-addresses-for-your-organization
-  - /restricting-email-notifications-for-your-organization
-  - /reviewing-the-audit-log-for-your-organization
-  - /reviewing-your-organizations-installed-integrations
+  - /managing-two-factor-authentication-for-your-organization
+  - /managing-security-settings-for-your-organization
 shortTitle: Seguridad organizacional
 ---
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
new file mode 100644
index 0000000000..a9769a5239
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your organization
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Teams
+permissions: Organization owners can access compliance reports for the organization.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "Compliance reports", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Leer más
+
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
new file mode 100644
index 0000000000..6c813260f9
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing security settings for your organization
+shortTitle: Manage security settings
+intro: 'You can manage security settings and review the audit log{% ifversion ghec %}, compliance reports,{% endif %} and integrations for your organization.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-security-and-analysis-settings-for-your-organization
+  - /managing-allowed-ip-addresses-for-your-organization
+  - /restricting-email-notifications-for-your-organization
+  - /reviewing-the-audit-log-for-your-organization
+  - /accessing-compliance-reports-for-your-organization
+  - /reviewing-your-organizations-installed-integrations
+---
+
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
new file mode 100644
index 0000000000..618e6d056a
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -0,0 +1,85 @@
+---
+title: Administrar las direcciones IP permitidas en tu organización
+intro: Puedes restringir el acceso a los activos de tu organización si configuras una lista de direcciones IP que se pueden conectar a ella.
+product: '{% data reusables.gated-features.allowed-ip-addresses %}'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Administrar las direcciones IP permitidas
+---
+
+Los propietarios de las organizaciones pueden administrar las direcciones IP permitidas en las mismas.
+
+## Acerca de las direcciones IP permitidas
+
+Puedes restringir el acceso a los activos de la organización configurando un listado de direcciones IP específicas permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
+
+Si configuras una lista de direcciones permitidas, también puedes elegir agregar automáticamente a ella cualquier dirección IP que hayas configurado para las {% data variables.product.prodname_github_apps %} que instales en tu organización. El creador de una {% data variables.product.prodname_github_app %} puede configurar una lista de direcciones permitidas para su aplicación, las cuales especifiquen las direcciones IP en las cuales se ejecuta esta. Al heredar la lista de direcciones permitidas en la tuya, estás evitando las solicitudes de conexión de la aplicación que se está rehusando. Para obtener más información, consulta la sección "[Permitir el acceso mediante {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)".
+
+También puedes configurar las direcciones IP permitidas para las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir políticas para la configuración de seguridad en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
+
+## Agregar una dirección IP permitida
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+
+## Habilitar direcciones IP permitidas
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. Haz clic en **Save ** (guardar).
+
+## Permitir el acceso mediante {% data variables.product.prodname_github_apps %}
+
+Si estás utilizando una lista de direcciones permitidas, también puedes elegir agregar automáticamente a ella cualquier dirección IP que hayas configurado para las {% data variables.product.prodname_github_apps %} que instales en tu organización.
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+Para obtener más información sobre cómo crear una lista de direcciones permitidas para una {% data variables.product.prodname_github_app %} que hayas creado, consulta la sección "[Administrar las direcciones IP permitidas para una GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Debajo de "Lista de direcciones IP permitidas", selecciona **Habilitar la configuración de la lista de direcciones IP permitidas para las GitHub Apps instaladas**. ![Casilla de verificación para permitir las direcciones IP de las GitHub Apps](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Haz clic en **Save ** (guardar).
+
+## Editar una dirección IP permitida
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+1. Da clic en **Actualizar**.
+
+## Eliminar una dirección IP permitida
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
+
+{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
new file mode 100644
index 0000000000..9ac4ab44f6
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -0,0 +1,171 @@
+---
+title: Administrar los parámetros de seguridad y análisis para tu organización
+intro: 'Puedes controlar las características que aseguran y analizan el código en los proyectos de tu organización en {% data variables.product.prodname_dotcom %}.'
+permissions: Organization owners can manage security and analysis settings for repositories in the organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Administrar el análisis & seguridad
+---
+
+## Acerca de la administración de los parámetros de seguridad y análisis
+
+{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar los repositorios en tu organización. Puedes administrar las características de seguridad y de análisis para todos los repositorios existentes que los miembros creen en tu organización. {% ifversion ghec %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, entonces también podrás administrar el acceso a estas características. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con una licencia de {% data variables.product.prodname_GH_advanced_security %} también pueden administrar el acceso a estas características. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## Mostrar la configuración de seguridad y de análisis
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+
+La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización.
+
+{% ifversion ghec %}Si tu organización pertenece a una empresa que tiene una licencia para {% data variables.product.prodname_GH_advanced_security %}, la págna también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %}
+
+{% ifversion ghes > 3.0 %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, la página también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %}
+
+{% ifversion ghae %}La página también contendrá opciones para habilitar e inhabilitar las características de la {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %}
+
+## Habilitar o inhabilitar una característica para todos los repositorios existentes
+
+Puedes habilitar o inhabilitar las características para todos los repositorios.
+{% ifversion fpt or ghec %}El impacto de tus cambios en los repositorios de tu organización se determina de acuerdo con su visibilidad:
+
+- **Gráfica de dependencias** - Tus cambios solo afectan a repositorios privados porque la característica siempre está habilitada para los repositorios públicos.
+- **{% data variables.product.prodname_dependabot_alerts %}** - Tus cambios afectan a todos los repositorios.
+- **{% data variables.product.prodname_dependabot_security_updates %}** - Tus cambios afectan a todos los repositorios.
+{%- ifversion ghec %}
+- **{% data variables.product.prodname_GH_advanced_security %}** - Tus cambios afectan únicamente a los repositorios privados, ya que la {% data variables.product.prodname_GH_advanced_security %} y las características relacionadas siempre se encuentran habilitadas para los repositorios públicos.
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Tus cambios afectan únicamente a los repositorios privados en donde la {% data variables.product.prodname_GH_advanced_security %} también se encuentra habilitada. El {% data variables.product.prodname_secret_scanning_caps %} siempre se encuentra habilitado para los repositorios públicos.
+{% endif %}
+
+{% endif %}
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
+2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. {% ifversion ghes > 3.0 or ghec %}El control para "{% data variables.product.prodname_GH_advanced_security %}" se encontrará inhabilitado si no tienes plazas disponibles en tu licencia de {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
+   {% ifversion fpt %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   {% endif %}
+   {% ifversion ghes > 3.2 %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+3. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización.
+   {% ifversion fpt or ghec %}
+   ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+4. Da clic en **Inhabilitar CARACTERÍSTICA** o en **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios en tu organización.
+   {% ifversion fpt or ghec %}
+   ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Botón para inhabilitar o habilitar la característica](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion ghae or ghes > 3.0 %}
+3. Haz clic en **Habilitar/Inhabilitar todas** o en **Habilitar/Inhabilitar para los repositorios elegibles** para confirmar el cambio. ![Botón para habilitar característica para todos los repositorios elegibles de la organización](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% endif %}
+
+   {% data reusables.security.displayed-information %}
+
+## Habilitar o inhabilitar una característica automáticamente cuando se agregan repositorios nuevos
+
+1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
+2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la características, habilita o inhabilitala predeterminadamente para los repositorios nuevos{% ifversion fpt or ghec %} o para todos los repositorios privados{% endif %} de tu organización.
+   {% ifversion fpt %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   {% endif %}
+
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
+
+## Permitir que el {% data variables.product.prodname_dependabot %} acceda a las dependencias privadas
+
+El {% data variables.product.prodname_dependabot %} puede verificar si hay referencias obsoletas de las dependencias en un proyecto y generar automáticamente una solicitud de cambios para actualizarlas. Para hacerlo, el {% data variables.product.prodname_dependabot %} debe tener acceso a todos los archivos de dependencia que sean el objetivo. Habitualmente, las actualizaciones de versión fallarán si una o más dependencias son inaccesibles. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)".
+
+Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios o en los registros de paquetes privados. Sin embargo, si una dependencia se encuentra en un repositorio privado de {% data variables.product.prodname_dotcom %} dentro de la misma organización que el proyecto que la utiliza, puedes permitir al {% data variables.product.prodname_dependabot %} actualizar la versión exitosamente si le otorgas acceso al repositorio en el que se hospeda.
+
+Si tu código depende de paquetes en un registro privado, puedes permitir que el {% data variables.product.prodname_dependabot %} actualice las versiones de estas dependencias si configuras esto a nivel del repositorio. Puedes hacer esto si agregas los detalles de autenticación al archivo _dependabot.yml_ para el repositorio. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)".
+
+Para permitir que el {% data variables.product.prodname_dependabot %} acceda a un repositorio privado de {% data variables.product.prodname_dotcom %}:
+
+1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
+1. Debajo de "Acceso del {% data variables.product.prodname_dependabot %} a repositorios privados", haz clic en **Agregar repositorios privados** o **Agregar repositorios internos y privados**. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. Comienza a teclear el nombre del repositorio que quieras permitir. ![El campo de búsqueda del repositorio con el menú desplegable filtrado](/assets/images/help/organizations/dependabot-private-repo-choose.png)
+1. Haz clic en el repositorio que quieras permitir.
+
+1. Opcionalmente, para eliminar un repositorio de la lista, a la derecha de este, haz clic en {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png)
+{% endif %}
+
+{% ifversion ghes > 3.0 or ghec %}
+
+## Eliminar el acceso a {% data variables.product.prodname_GH_advanced_security %} desde los repositorios individuales de una organización
+
+Puedes administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} para un repositorio desde su pestaña de "Configuración". Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". Sin embargo, también puedes inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} para un reositorio desde la pestaña de "Configuración" de la organización.
+
+1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
+1. Para encontrar una lista de todos los repositorios de tu organización que tengan habilitada la {% data variables.product.prodname_GH_advanced_security %}, desplázate hasta la sección "repositorios con {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) La tabla lista la cantidad de confirmantes únicos para cada repositorio. Esta es la cantidad de plazas que puedes liberar en tus licencias si eliminas el acceso a {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".
+1. Para eliminar el acceso a la {% data variables.product.prodname_GH_advanced_security %} desde un repositorio y liberar plazas que utilice cualquier confirmante y que son únicas en ese repositorio, haz clic en el {% octicon "x" aria-label="X symbol" %} adyacente.
+1. En el diálogo de confirmación, da clic en **Eliminar repositorio** para eliminar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %}.
+
+{% note %}
+
+**Nota:** Si eliminas el acceso de un repositorio a la {% data variables.product.prodname_GH_advanced_security %}, deberás comunicarte con el equipo de desarrollo afectado para que sepan que este cambio se hizo apropósito. Esto garantiza que no pierdan tiempo en depurar las ejecuciones fallidas del escaneo de código.
+
+{% endnote %}
+
+{% endif %}
+
+## Leer más
+
+- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Administrar las vulnerabilidades en las dependencias de tus proyectos](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Mantener tus dependencias actualizacas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..28bd732a2e
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,47 @@
+---
+title: Restringir las notificaciones por correo electrónico para tu organización
+intro: 'Para prevenir que se fugue la información de la organización en la scuentas personales de correo electrónico, puedes restringir los dominios en donde los miembros pueden recibir este tipo de notificaciones sobre la actividad de la organización.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '>=3.2'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: Restringir las notificaciones por correo electrónico
+---
+
+## Acerca de las restricciones de correo electrónico
+
+Cuando se habilitan las notificaciones por correo electrónico restringidas en una organización, los miembros solo pueden utilizar direcciones de correco electrónico asociadas con un dominio aprobado o verificado para recibir este tipo de notificaciones sobre la actividad de la organización. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Los colabores externos no están sujetos a las restricciones en las notificaciones por correo electrónico para los dominios verificados o aprobados. Para obtener más información sobre los colaboradores externos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
+
+Si tu organización pertenece a una cuenta empresarial, los miembros de dicha organización podrán recibir notificaciones de cualquier dominio que verifique o apruebe esta cuenta, adicionalmente a cualquier dominio que la misma organización verifique o apruebe. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
+
+## Restringir las notificciones por correo electrónico
+
+Antes de que puedas restringir las notificaciones por correo electrónico para tu organización, debes verificar o aprobar por lo menos un dominio para la organización o un propietario de la empresa debe haber verificado o aprobado por lo menos un dominio para la cuenta empresarial.
+
+Para obtener más información acerca de verificar y aprobar los dominios para una organización, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
new file mode 100644
index 0000000000..a611d0b13c
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -0,0 +1,772 @@
+---
+title: Revisar el registro de auditoría para tu organización
+intro: 'El registro de auditoría les permite a los administradores de la organización revisar rápidamente las acciones que realizaron los miembros de la organización. Incluye detalles como quién realizó la acción, de qué acción se trata y cuándo se realizó.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-the-audit-log-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization
+  - /organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Revisar las bitácoras de auditoría
+---
+
+## Acceder al registro de auditoría
+
+La bitácora de auditoría lista eventos que activan las actividades que afectan tu organización dentro del mes actual y los seis meses anteriores. Solo los propietarios pueden acceder al registro de auditoría de una organización.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+
+## Buscar el registro de auditoría
+
+{% data reusables.audit_log.audit-log-search %}
+
+### Búsqueda basada en la acción realizada
+
+Para buscar eventos específicos, utiliza el calificador `action` en tu consulta. Las acciones detalladas en el registro de auditoría se agrupan dentro de las siguientes categorías:
+
+| Nombre de la categoría                                                                                                                                                                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`cuenta`](#account-category-actions)                                                                                                                                                                                                                                             | Contiene todas las actividades relacionadas con tu cuenta de organización.                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                            | Contiene todas las actividades relacionadas con darle crédito a un contribuyente por una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".                                                           |
+| [`facturación`](#billing-category-actions)                                                                                                                                                                                                                                        | Contiene todas las actividades relacionadas con la facturación de tu organización.                                                                                                                                                                                                                                                                                                                                                                                |
+| [`business`](#business-category-actions)                                                                                                                                                                                                                                          | Contiene actividades relacionadas con los ajustes de negocios para una empresa.                                                                                                                                                                                                                                                                                                                                                                                   |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                      | Contiene todas las actividades relacionadas con los codespaces de tu organización. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                        | Contiene actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_alerts %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".                                                                                                |
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                    | Contiene las actividades de configuración a nivel de organización para las {% data variables.product.prodname_dependabot_alerts %} en los repositorios nuevos que se crearon en la organización.                                                                                                                                                                                                                                                                |
+| [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                    | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)".                                                        |
+| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions)                                                                                                                                                                                | Contiene las actividades de configuración a nivel de organización para las {% data variables.product.prodname_dependabot_security_updates %} para los repositorios nuevos que se crean en ella.{% endif %}{% ifversion fpt or ghec %}
+| [`dependency_graph`](#dependency_graph-category-actions)                                                                                                                                                                                                                          | Contiene las actividades de configuración a nivel de organización para las gráficas de dependencia de los repositorios. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".                                                                                                                                                                   |
+| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions)                                                                                                                                                                                                      | Contiene las actividades de configuración a nivel de organización para los repositorios nuevos que se crean en ella.{% endif %}
+| [`discussion_post`](#discussion_post-category-actions)                                                                                                                                                                                                                            | Contiene todas las actividades relacionadas con los debates publicados en una página de equipo.                                                                                                                                                                                                                                                                                                                                                                   |
+| [`discussion_post_reply`](#discussion_post_reply-category-actions)                                                                                                                                                                                                                | Contiene todas las actividades relacionadas con las respuestas a los debates que se publican en una página de equipo.{% ifversion fpt or ghes or ghec %}
+| [`empresa`](#enterprise-category-actions)                                                                                                                                                                                                                                         | Contiene las actividades relacionadas con la configuración de la empresa.                                                                                                                                                                                                                                                                                                                                                                                         |{% endif %}
+| [`gancho`](#hook-category-actions)                                                                                                                                                                                                                                                | Contiene todas las actividades relacionadas con los webhooks.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| [`integration_installation_request`](#integration_installation_request-category-actions)                                                                                                                                                                                          | Contiene todas las actividades relacionadas con las solicitudes de los miembros de la organización para que los propietarios aprueben las integraciones para el uso en la organización.                                                                                                                                                                                                                                                                           |
+| [`ip_allow_list`](#ip_allow_list)                                                                                                                                                                                                                                                 | Contains activities related to enabling or disabling the IP allow list for an organization.                                                                                                                                                                                                                                                                                                                                                                       |
+| [`ip_allow_list_entry`](#ip_allow_list_entry)                                                                                                                                                                                                                                     | Contiene las actividades relacionadas con la creación, borrado y edición de una entrada en una lista de direcciones IP permitidas para una organización.                                                                                                                                                                                                                                                                                                          |
+| [`propuesta`](#issue-category-actions)                                                                                                                                                                                                                                            | Contiene las actividades relacionadas con borrar una propuesta.                                                                                                                                                                                                                                                                                                                                                                                                   |{% ifversion fpt or ghec %}
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions)                                                                                                                                                                                            | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                                        |
+| [`marketplace_listing`](#marketplace_listing-category-actions)                                                                                                                                                                                                                    | Contiene todas las actividades relacionadas con el listado de apps en {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`members_can_create_pages`](#members_can_create_pages-category-actions)                                                                                                                                                                                                          | Contiene todas las actividades relacionadas con administrar la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %}
+| [`org`](#org-category-actions)                                                                                                                                                                                                                                                    | Contiene actividades relacionadas con la membrecía organizacional.{% ifversion ghec %}
+| [`org_credential_authorization`](#org_credential_authorization-category-actions)                                                                                                                                                                                                  | Contiene todas las actividades relacionadas con la autorización de credenciales para su uso con el inicio de sesión único de SAML. {% endif %}{% ifversion fpt or ghes or ghae or ghec %}
+| [`organization_label`](#organization_label-category-actions)                                                                                                                                                                                                                      | Contiene todas las actividades relacionadas con las etiquetas predeterminadas para los repositorios de tu organización.{% endif %}
+| [`oauth_application`](#oauth_application-category-actions)                                                                                                                                                                                                                        | Contiene todas las actividades relacionadas con las Apps de OAuth.{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`paquetes`](#packages-category-actions)                                                                                                                                                                                                                                          | Contiene todas las actividades relacionadas con el {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions)                                                                                                                                                                                                                              | Contiene todas las actividades relacionadas con la manera en que tu organización le paga a GitHub.{% endif %}
+| [`profile_picture`](#profile_picture-category-actions)                                                                                                                                                                                                                            | Contiene todas las actividades relacionadas con la foto de perfil de tu organización.                                                                                                                                                                                                                                                                                                                                                                             |
+| [`project`](#project-category-actions)                                                                                                                                                                                                                                            | Contiene todas las actividades relacionadas con los tableros de proyecto.                                                                                                                                                                                                                                                                                                                                                                                         |
+| [`rama_protegida`](#protected_branch-category-actions)                                                                                                                                                                                                                            | Contiene todas las actividades relacionadas con las ramas protegidas.                                                                                                                                                                                                                                                                                                                                                                                             |
+| [`repo`](#repo-category-actions)                                                                                                                                                                                                                                                  | Contiene las actividades relacionadas con los repositorios que le pertenecen a tu organización.{% ifversion fpt or ghec %}
+| [`repository_advisory`](#repository_advisory-category-actions)                                                                                                                                                                                                                    | Contiene actividades a nivel de repositorio relacionadas con las asesorías de seguridad en la {% data variables.product.prodname_advisory_database %}.  Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".                                                                                 |
+| [`repository_content_analysis`](#repository_content_analysis-category-actions)                                                                                                                                                                                                    | Contiene todas las actividades relacionadas con [habilitar o inhabilitar el uso de datos para un repositorio privado](/articles/about-github-s-use-of-your-data){% endif %}{% ifversion fpt or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions)                                                                                                                                                                                                    | Contiene las actividades a nivel de repositorio para habilitar o inhabilitar la gráfica de dependencias para un                                                                                                                                                                                                                                                                                                                                                   |
+| repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".{% endif %}{% ifversion ghes or ghae or ghec %} |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions)                                                                                                                                                                                                      | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning).                                                                                                                                                                                                                              |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions)                                                                                                                                                                                              | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
+| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions)                                                                                                                                                                                            | Contiene actividades de configuración a nivel de repositorio para las {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
+| [`rol`](#role-category-actions)                                                                                                                                                                                                                                                   | Contiene todas las actividades relacionadas con los [roles de repositorio personalziados](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`secret_scanning`](#secret_scanning-category-actions)                                                                                                                                                                                                                            | Contiene las actividades de configuración a nivel de organización para el escaneo de secretos en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning).                                                                                                                                                                                     |
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions)                                                                                                                                                                                                        | Contiene las actividades de configuración a nivel de organización para el escane de secretos para los repositorios nuevos que se crean en ella.                                                                                                                                                                                                                                                                                                                   |{% endif %}{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions)                                                                                                                                                                                                                                          | Contiene todas los eventos relacionados con los botones del patrocinador (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
+| [`equipo`](#team-category-actions)                                                                                                                                                                                                                                                | Contiene todas las actividades relacionadas con los equipos en tu organización.                                                                                                                                                                                                                                                                                                                                                                                   |
+| [`team_discussions`](#team_discussions-category-actions)                                                                                                                                                                                                                          | Contiene actividades relacionadas a administrar los debates de equipo para una organización.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| [`flujos de trabajo`](#workflows-category-actions)                                                                                                                                                                                                                                | Contiene actividades relacionadas con los flujos de trabajo de las {% data variables.product.prodname_actions %}.{% endif %}
+
+Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo:
+
+  * `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo.
+  * `-action:hook` excluye todos los eventos en la categoría de webhook.
+
+Cada categoría tiene un conjunto de acciones asociadas que puedes filtrar. Por ejemplo:
+
+  * `action:team.create` encuentra todos los eventos donde se creó un equipo.
+  * `-action:hook.events_changed` excluye todos los eventos en que se modificaron los eventos sobre un webhook.
+
+### Búsqueda basada en el momento de la acción
+
+Utiliza el calificador `created` para filtrar los eventos en la bitácora de auditoría con base en su fecha de ocurrencia. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+Por ejemplo:
+
+  * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014.
+  * `created:>=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o después.
+  * `created:<=2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014 o antes.
+  * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014.
+
+
+{% note %}
+
+**Nota**: La bitácora de auditoría contiene datos del mes actual y de cada día de los seis meses anteriores.
+
+{% endnote %}
+
+### Búsqueda basada en la ubicación
+
+Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora de auditoría con base en el país en donde se originaron. Puedes utilizar un código corto de dos letras del país o el nombre completo. Ten presente que los países con espacios en sus nombres se deben poner entre comillas. Por ejemplo:
+
+  * `country:de` encuentra todos los eventos ocurridos en Alemania.
+  * `country:Mexico` encuentra todos los eventos ocurridos en México.
+  * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos.
+
+{% ifversion fpt or ghec %}
+## Exportar el registro de auditoría
+
+{% data reusables.audit_log.export-log %}
+{% data reusables.audit_log.exported-log-keys-and-values %}
+{% endif %}
+
+## Utilizar la API de bitácoras de auditoría
+
+Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{% ifversion fpt or ghec %} o la API de REST{% endif %}.
+
+{% ifversion fpt or ghec %}
+La API de auditoría requiere {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+
+### Utilizar la API de GraphQL
+
+{% endif %}
+
+{% note %}
+
+**Nota**: La API de bitácora de auditoría de GraphQL está disponible para las organizaciones que utilizan {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %}
+
+{% endnote %}
+
+Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de GraphQL para bitácoras de auditoría para mantener copias de tus datos de bitácoras de auditoría y monitorear:
+{% data reusables.audit_log.audit-log-api-info %}
+
+{% ifversion fpt or ghec %}
+Ten en cuenta que no puedes recuperar los eventos de Git utilizando la API de GraphQL. Para recuperar eventos de Git, utiliza mejor la API de REST. Para obtener más información, consulta las "[acciones de la categoría `git`](#git-category-actions)".
+{% endif %}
+
+La respuesta de GraphQL puede incluir datos de hasta 90 a 120 días.
+
+Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros nuevos de la organización agregados a tu organización. Para obtener más información, consulta la "[Bitácora de Auditoría de la API de GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)".
+
+{% ifversion fpt or ghec %}
+
+### Utilizar la API de REST
+
+{% note %}
+
+**Nota:** La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}.
+
+{% endnote %}
+
+Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de REST de bitácoras de auditoría para mantener copias de tus bitácoras de auditoría y monitorear:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+Para obtener más información sobre la API de REST del log de auditoría, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
+
+{% endif %}
+
+## Acciones de la bitácora de auditoría
+
+Un resumen de algunas de las acciones más comunes que se registran como eventos en la bitácora de auditoría.
+
+{% ifversion fpt or ghec %}
+### Acciones de la categoría `account`
+
+| Acción                                                          | Descripción                                                                                                                                                                                              |
+| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `billing_plan_change (cambio del plan de facturación)`          | Se activa cuando cambia el [ciclo de facturación](/articles/changing-the-duration-of-your-billing-cycle) de una organización.                                                                            |
+| `plan_change (cambio de plan)`                                  | Se activa cuando cambia la [suscripción](/articles/about-billing-for-github-accounts) de una organización.                                                                                               |
+| `pending_plan_change (cambio de plan pendiente)`                | Se activa cuando un propietario de la organización o gerente de facturación [cancela o baja de categoría una suscripción paga](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). |
+| `pending_subscription_change (cambio de suscripción pendiente)` | Se activa cuando comienza o se vence una [{% data variables.product.prodname_marketplace %} prueba gratuita](/articles/about-billing-for-github-marketplace/).                                           |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Acciones de la categoría `advisory_credit`
+
+| Acción               | Descripción                                                                                                                                                                                                                             |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`             | Se activa cuando alguien acepta el crédito de una asesoría de seguridad. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". |
+| `create (crear)`     | Se activa cuando el administrador de una asesoría de seguridad agrega a alguien a la sección de crédito.                                                                                                                                |
+| `decline`            | Se activa cuando alguien rechaza el crédito para una asesoría de seguridad.                                                                                                                                                             |
+| `destroy (destruir)` | Se activa cuando el administrador de una asesoría de seguridad elimina a alguien de la sección de crédito.                                                                                                                              |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### acciones de la categoría `billing`
+
+| Acción                                              | Descripción                                                                                                                                                 |
+| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando tu organización [cambia la manera en que paga {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). |
+| `change_email (cambiar correo electrónico)`         | Se activa cuando cambia la [dirección de correo electrónico de facturación](/articles/setting-your-billing-email) de tu organización.                       |
+{% endif %}
+
+### Acciones de la categoría `business`
+
+| Acción                                 | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Se activa cuando el ajuste para solicitar aprobaciones para los flujos de trabajo desde las bifurcaciones públicas se cambia en una empresa. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)".{% endif %}
+| `set_actions_retention_limit`          | Se activa cuando el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %} se cambian en una empresa. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_actions %} en tu empresa]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)".{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`         | Se activa cuando se cambia la política de flujos de trabajo sobre las bifurcaciones de repositorios privados. Para obtener más información, consulta la sección "{% ifversion fpt or ghec%}[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Habilitar los flujos de trabajo para las bifurcaciones de repositorios privados](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}".{% endif %}
+
+{% ifversion fpt or ghec %}
+### acciones de la categoría `codespaces`
+
+| Acción                       | Descripción                                                                                                                                                                                                                                                   |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`             | Se activa cuando un usuario [crea un codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                              |
+| `resume`                     | Se activa cuando un usuario reanuda un codesapce suspendido.                                                                                                                                                                                                  |
+| `delete`                     | Se activa cuando un usuario [borra un codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                             |
+| `create_an_org_secret`       | Se activ cuando un usuario crea un [secreto para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel de la organización |
+| `update_an_org_secret`       | Se activa cuando un usuario actualiza un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional.  |
+| `remove_an_org_secret`       | Se activa cuando un usuario elimina un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional.    |
+| `manage_access_and_security` | Se activa cuando un usuario actualiza [a cuáles repositorios puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.2 %}
+### Acciones de la categoría `dependabot_alerts`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de organización inhabilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% ifversion fpt or ghec %}privados {% endif %}existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de la organización habilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% ifversion fpt or ghec %}privados {% endif %} existentes.                                                                                                                                                                                                                                               |
+
+### Acciones de la categoría `dependabot_alerts_new_repos`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando el propietario de una organización inhabilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% ifversion fpt or ghec %}privados {% endif %} nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% ifversion fpt or ghec %}privados {% endif %}nuevos.                                                                                                                                                                                                                                                        |
+
+### Acciones de la categoría `dependabot_security_updates`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios existentes.                                                                                                                                                                                                                                                      |
+
+### Acciones de la categoría `dependabot_security_updates_new_repos`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de la organización habilita las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios nuevos.                                                                                                                                                                                                                                                   |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Acciones de la categoría `dependency_graph`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios existentes. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios existentes.                                                                                                                                                                                                                                                   |
+
+### Acciones de la categoría `dependency_graph_new_repos`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita la gráfica de dependencias para todos los repositorios nuevos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de la organización habilita la gráfica de dependencias para todos los repositorios nuevos.                                                                                                                                                                                                                                                   |
+{% endif %}
+
+### acciones de la categoría `discussion_post`
+
+| Acción               | Descripción                                                                                                                 |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `actualización`      | Se activa cuando se edita [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). |
+| `destroy (destruir)` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).             |
+
+### acciones de la categoría `discussion_post_reply`
+
+| Acción               | Descripción                                                                                                                                    |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `actualización`      | Se activa cuando se edita [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment).    |
+| `destroy (destruir)` | Se activa cuando se elimina [una respuesta a una publicación de debate de equipo](/articles/managing-disruptive-comments/#deleting-a-comment). |
+
+{% ifversion fpt or ghes or ghec %}
+### acciones de la categoría `enterprise`
+
+{% data reusables.actions.actions-audit-events-for-enterprise %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### acciones de la categoría `environment`
+
+| Acción                  | Descripción                                                                                                                                                                                 |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create_actions_secret` | Se activa cuando se crea un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)".        |
+| `delete`                | Se activa cuando se borra un ambiente. Para obtener más información, consulta la sección "[Borrar un ambiente](/actions/reference/environments#deleting-an-environment)".                   |
+| `remove_actions_secret` | Se activa cuando se elimina a un secreto de un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)".   |
+| `update_actions_secret` | Se activa cuando se actualiza a un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". |
+{% endif %}
+
+{% ifversion ghae %}
+### Acciones de la categoría `external_group`
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% endif %}
+
+{% ifversion ghae %}
+### Acciones de la categoría `external_identity`
+
+{% data reusables.saml.external-identity-audit-events %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### acciones de la categoría `git`
+
+{% note %}
+
+**Nota:** Para acceder a los eventos de Git en la bitácora de auditoría, debes utilizar la API de la bitácora de auditoría de REST. La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
+
+{% endnote %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+| Acción      | Descripción                                              |
+| ----------- | -------------------------------------------------------- |
+| `clon`      | Se activa cuando se clona un repositorio.                |
+| `recuperar` | Se activa cuando se recuperan cambios de un repositorio. |
+| `subir`     | Se activa cuando se suben cambios a un repositorio.      |
+
+{% endif %}
+
+### acciones de la categoría `hook`
+
+| Acción                                      | Descripción                                                                                                                   |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`                            | Se activa cuando [se agregó un enlace nuevo](/articles/creating-webhooks)a un repositorio que le pertenece a tu organización. |
+| `config_changed (configuración modificada)` | Se activa cuando se modifica la configuración de un enlace existente.                                                         |
+| `destroy (destruir)`                        | Se activa cuando se eliminó un enlace existente de un repositorio.                                                            |
+| `events_changed (eventos modificados)`      | Se activa cuando se modificaron los eventos en un enlace.                                                                     |
+
+### Acciones de la categoría`integration_installation_request`
+
+| Acción           | Descripción                                                                                                                                                                                                                         |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando un miembro de la organización solicita que un propietario de la organización instale una integración para utilizar en la organización.                                                                             |
+| `close`          | Se activa cuando un propietario de la organización aprueba o rechaza una solicitud para instalar una integración para que se utilice en una organización, o cuando la cancela el miembro de la organización que abrió la solicitud. |
+
+### `ip_allow_list` category actions
+
+| Acción                       | Descripción                                                                                                                                    |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `habilitar`                  | Se activa cuando se habilita una lista de direcciones IP permitidas para una organización.                                                     |
+| `inhabilitar`                | Se activa cuando se inhabilita una lista de direcciones IP permitidas para una organización.                                                   |
+| `enable_for_installed_apps`  | Se activa cuando una lista de IP permitidas se habilitó para las {% data variables.product.prodname_github_apps %} instaladas.               |
+| `disable_for_installed_apps` | Se activa cuando se inhabilitó una lista de direcciones IP permitidas para las {% data variables.product.prodname_github_apps %} instaladas. |
+
+### Acciones de la categoría `ip_allow_list_entry`
+
+| Acción               | Descripción                                                                             |
+| -------------------- | --------------------------------------------------------------------------------------- |
+| `create (crear)`     | Se activa cuando una dirección IP se agregó a una lista de direcciones IP permitidas.   |
+| `actualización`      | Se activa cuando una dirección IP o su descripción se cambió.                           |
+| `destroy (destruir)` | Se activa cuando una dirección IP se eliminó de una lista de direcciones IP permitidas. |
+
+### acciones de la categoría `issue`
+
+| Acción               | Descripción                                                                                                                                                                                     |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `destroy (destruir)` | Se activa cuando un propietario de la organización o alguna persona con permisos de administrador en un repositorio elimina una propuesta de un repositorio que le pertenece a la organización. |
+
+{% ifversion fpt or ghec %}
+
+### acciones de la categoría `marketplace_agreement_signature`
+
+| Acción           | Descripción                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. |
+
+### acciones de la categoría `marketplace_listing`
+
+| Acción                        | Descripción                                                                                                  |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `aprobar`                     | Se activa cuando se aprueba tu lista para ser incluida en {% data variables.product.prodname_marketplace %}. |
+| `create (crear)`              | Se activa cuando creas una lista para tu app en {% data variables.product.prodname_marketplace %}.           |
+| `delist (quitar de la lista)` | Se activa cuando se elimina tu lista de {% data variables.product.prodname_marketplace %}.                   |
+| `redraft`                     | Se activa cuando tu lista se vuelve a colocar en estado de borrador.                                         |
+| `reject (rechazar)`           | Se activa cuando no se acepta la inclusión de tu lista en {% data variables.product.prodname_marketplace %}. |
+
+{% endif %}
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+
+### Acciones de la categoría `members_can_create_pages`
+
+Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)".
+
+| Acción        | Descripción                                                                                                                                                                      |
+|:------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `habilitar`   | Se activa cuando el propietario de una organización habilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización.   |
+| `inhabilitar` | Se activa cuando el propietario de una organización inhabilita la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. |
+
+{% endif %}
+
+### acciones de la categoría `org`
+
+| Acción                                              | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member (agregar miembro)`                      | Se activa cuando un usuario se une a una organización.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_policy_selected_member_disabled` | Se activa cuando un propietario de empresa previene que las carcaterísticas de la {% data variables.product.prodname_GH_advanced_security %} se habiliten para los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `advanced_security_policy_selected_member_enabled`  | Se activa cuando un propietario de empresa permite que se habiliten las características de la {% data variables.product.prodname_GH_advanced_security %} en los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %}
+| `audit_log_export`                                  | Se activa cuando un administrador de la organización [crea una exportación del registro de auditoría de la organización](#exporting-the-audit-log). Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta.                                                                                                                                                                                                         |
+| `block_user`                                        | Se activa cuando un propietario de la organización [bloquea a un usuario para que no pueda acceder a los repositorios de la organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).                                                                                                                                                                                                                                                                                                     |
+| `cancel_invitation`                                 | Se activa cuando se revocó una invitación de la organización.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |{% endif %}{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                             | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se crea para una organización. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)".{% endif %}                                                                                                                                                                                                                      |{% ifversion fpt or ghec %}
+| `disable_oauth_app_restrictions`                    | Se activa cuando un propietario [inhabilita {% data variables.product.prodname_oauth_app %} restricciones de acceso](/articles/disabling-oauth-app-access-restrictions-for-your-organization) para tu organización.{% ifversion ghec %}
+| `disable_saml`                                      | Se activa cuando un administrador de la organización inhabilita el inicio de sesión único SAML para una organización.{% endif %}{% endif %}
+| `disable_member_team_creation_permission`           | Se activa cuando un propietario de la organización limita la creación de equipos para los propietarios. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `disable_two_factor_requirement`                    | Se activa cuando un propietario inhabilita el requisito de autenticación bifactorial para todos los miembros{% ifversion fpt or ghec %}, gerentes de facturación, {% endif %} y colaboradores externos en una organización.{% endif %}{% ifversion fpt or ghec %}
+| `enable_oauth_app_restrictions`                     | Se activa cuando un propietario [habilita las restricciones de acceso de una {% data variables.product.prodname_oauth_app %} ](/articles/enabling-oauth-app-access-restrictions-for-your-organization) para tu organización.{% ifversion ghec %}
+| `enable_saml`                                       | Se activa cuando un administrador de la organización [habilita el inicio de sesión único SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para una organización.{% endif %}{% endif %}
+| `enable_member_team_creation_permission`            | Se activa cuando un propietario de la organización permite que los miembros creen equipos. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `enable_two_factor_requirement`                     | Se activa cuando un propietario requiere la autenticación bifactorial para todos los miembros{% ifversion fpt or ghec %}, gerentes de facturación{% endif %} y colaboradores externos en una organización.{% endif %}{% ifversion fpt or ghec %}
+| `invite_member`                                     | Se activa cuando [se invitó a un usuario nuevo a unirse a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization).                                                                                                                                                                                                                                                                                                                                                         |
+| `oauth_app_access_approved`                         | Se activa cuando un propietario [le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/).                                                                                                                                                                                                                                                                                                                                                  |
+| `oauth_app_access_denied`                           | Se activa cuando un propietario [inhabilita un acceso de {% data variables.product.prodname_oauth_app %} anteriormente aprobado](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) para tu organización.                                                                                                                                                                                                                                                                                           |
+| `oauth_app_access_requested`                        | Se activa cuando un miembro de la organización solicita que un propietario otorgue un acceso de {% data variables.product.prodname_oauth_app %} para tu organización.{% endif %}
+| `register_self_hosted_runner`                       | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)".                                                                                                                                                                                                                                                |
+| `remove_actions_secret`                             | Se activa cuando se elimina un secreto de {% data variables.product.prodname_actions %}.{% ifversion fpt or ghec %}
+| `remove_billing_manager`                            | Se activa cuando un [propietario elimina un gerente de facturación de una organización](/articles/removing-a-billing-manager-from-your-organization/) o cuando [se requiere autenticación de dos factores en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no usa la 2FA o inhabilita la 2FA. 
+{% endif %}
+| `remove_member (eliminar miembro)`                  | Se activa cuando un [propietario elimina a un miembro de una organización](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. También se activa cuando un [miembro de la organización se elimina a sí mismo](/articles/removing-yourself-from-an-organization/) de una organización. |
+| `remove_outside_collaborator`                       | Se activa cuando un propietario elimina a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no utiliza la 2FA o la inhabilita{% endif %}.                                                                                                                                                                                                       |
+| `remove_self_hosted_runner`                         | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)".                                                                                                                                                                                                                                                                      |{% ifversion ghec %}
+| `revoke_external_identity`                          | Se actuva cuando un dueño de una organización retira la identidad vinculada de un mimebro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)".                                                                                                                     |
+| `revoke_sso_session`                                | Se activa cuando el dueño de una organización retira la sesión de SAML de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)".                                                                                                                          |{% endif %}
+| `runner_group_created`                              | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)".                                                                                                                                                                                             |
+| `runner_group_removed`                              | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".                                                                                                                                                                                                                                  |
+| `runner_group_updated`                              | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".                                                                                                                                                               |
+| `runner_group_runners_added`                        | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección [Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).                                                                                                                                                                                                                                      |
+| `runner_group_runner_removed`                       | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)".                                                                                                                                                                                                                     |
+| `runner_group_runners_updated`                      | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`                         | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                            |
+| `self_hosted_runner_offline`                        | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Verificar el estado de un ejecutor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`                        | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy`              | Se activa cuando se cambia el ajuste para requerir aprobaciones para los flujos de trabajo desde las bifurcaciones públicas en una organización. Para obtener más información, consulta la sección "[Requerir la aprobación para los flujos de trabajo desde las bifurcaciones públicas](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)".{% endif %}
+| `set_actions_retention_limit`                       | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)".{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`                      | Se activa cuando se cambia la política de flujos de trabajo sobre las bifurcaciones de repositorios privados. Para obtener más información, consulta la sección "[Habilitar los flujos de trabajo para las bifurcaciones de repositorios privados](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)".{% endif %}{% ifversion fpt or ghec %}
+| `unblock_user`                                      | Se acvita cuando el propietario de una organización [desbloquea a un usuario de la misma](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                             | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %}
+| `update_new_repository_default_branch_setting`      | Se activa cuando el propietario cambia el nombre de la rama predeterminada para los repositorios nuevos de la organización. Para obtener más información, consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)".                                                                                                                                     |
+| `update_default_repository_permission`              | Se activa cuando un propietario cambia el nivel de permiso al repositorio predeterminado para los miembros de la organización.                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `update_member`                                     | Se activa cuando un propietario cambia el rol de una persona de propietario a miembro o de miembro a propietario.                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `update_member_repository_creation_permission`      | Se activa cuando un propietario cambia el permiso de creación de repositorios para miembros de la organización.{% ifversion fpt or ghec %}
+| `update_saml_provider_settings`                     | Se activa cuando se actualizan las configuraciones del proveedor SAML de una organización.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `update_terms_of_service`                           | Se activa cuando una organización cambia de los Términos de servicio estándar a los Términos de servicio corporativos. Para obtener más información, consulta "[Subir de categoría a Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".{% endif %}
+
+{% ifversion ghec %}
+### acciones de la categoría `org_credential_authorization`
+
+| Acción         | Descripción                                                                                                                                                                                                          |
+| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grant`        | Se activa cuando un miembro [autoriza credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                                     |
+| `deauthorized` | Se activa cuando un miembro [quita la autorización de credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                     |
+| `revoke`       | Se activa cuando un propietario [revoca las credenciales autorizadas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). |
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghae or ghec %}
+### Acciones de la categoría `organization_label`
+
+| Acción               | Descripción                                           |
+| -------------------- | ----------------------------------------------------- |
+| `create (crear)`     | Se activa cuando se crea una etiqueta por defecto.    |
+| `actualización`      | Se activa cuando se edita una etiqueta por defecto.   |
+| `destroy (destruir)` | Se activa cuando se elimina una etiqueta por defecto. |
+
+{% endif %}
+
+### acciones de la categoría `oauth_application`
+
+| Acción                               | Descripción                                                                                                              |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
+| `create (crear)`                     | Se activa cuando se crea una {% data variables.product.prodname_oauth_app %} nueva.                                    |
+| `destroy (destruir)`                 | Se activa cuando se elimina una {% data variables.product.prodname_oauth_app %} existente.                             |
+| `reset_secret (restablecer secreto)` | Se activa cuando se restablece un secreto de cliente de {% data variables.product.prodname_oauth_app %}.               |
+| `revoke_tokens (revocar tokens)`     | Se activa cuando se revocan los tokens de usuario de una {% data variables.product.prodname_oauth_app %}.              |
+| `transferencia`                      | Se activa cuando se transfiere una {% data variables.product.prodname_oauth_app %} existente a una organización nueva. |
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+### Acciones de la categoría `packages`
+
+| Acción                      | Descripción                                                                                                                                                                                                           |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `package_version_published` | Se activa cuando se publica una versión del paquete.                                                                                                                                                                  |
+| `package_version_deleted`   | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". |
+| `package_deleted`           | Se activa cuando se borra un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".               |
+| `package_version_restored`  | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". |
+| `package_restored`          | Se activa cuando se restablece un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".          |
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### acciones de la categoría `payment_method`
+
+| Acción           | Descripción                                                                                                   |
+| ---------------- | ------------------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando se agrega un método de pago nuevo, como una tarjeta de crédito nueva o una cuenta de PayPal. |
+| `actualización`  | Se activa cuando se actualiza un método de pago existente.                                                    |
+
+{% endif %}
+
+### acciones de la categoría `profile_picture`
+| Acción        | Descripción                                                                    |
+| ------------- | ------------------------------------------------------------------------------ |
+| actualización | Se activa cuando estableces o actualizas la foto de perfil de tu organización. |
+
+### acciones de la categoría `project`
+
+| Acción                                                          | Descripción                                                                                                                                                              |
+| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create (crear)`                                                | Se activa cuando se crear un tablero de proyecto.                                                                                                                        |
+| `link`                                                          | Se activa cuando un repositorio se vincula a un tablero de proyecto.                                                                                                     |
+| `rename (renombrar)`                                            | Se activa cuando se renombra un tablero de proyecto.                                                                                                                     |
+| `actualización`                                                 | Se activa cuando se actualiza un tablero de proyecto.                                                                                                                    |
+| `delete`                                                        | Se activa cuando se elimina un tablero de proyecto.                                                                                                                      |
+| `unlink (desvincular)`                                          | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto.                                                                                       |
+| `update_org_permission (actualizar permiso de la organización)` | Se activa cuando se cambia o elimina el permiso al nivel de base para todos los miembros de la organización.                                                             |
+| `update_team_permission (actualizar permiso del equipo)`        | Se activa cuando se cambia el nivel de permiso del tablero de proyecto de un equipo o cuando se agrega un equipo a un tablero de proyecto o se elimina de este.          |
+| `update_user_permission`                                        | Se activa cuando un miembro de la organización o colaborador externo se agrega a un tablero de proyecto o se elimina de este, o cuando se le cambia su nivel de permiso. |
+
+### acciones de la categoría `protected_branch`
+
+| Acción                                                                                                                      | Descripción                                                                                                                                                                                        |
+| --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`                                                                                                            | Se activa cuando se habilita la protección de rama en una rama.                                                                                                                                    |
+| `destroy (destruir)`                                                                                                        | Se activa cuando se inhabilita la protección de rama en una rama.                                                                                                                                  |
+| `update_admin_enforced (actualizar administrador aplicado)`                                                                 | Se activa cuando se aplica la protección de rama para los administradores del repositorio.                                                                                                         |
+| `update_require_code_owner_review (actualizar requerir revisión del propietario del código)`                                | Se activa cuando se actualiza en una rama la aplicación de revisión del propietario del código requerida.                                                                                          |
+| `dismiss_stale_reviews (descartar revisiones en espera)`                                                                    | Se activa cuando se actualiza en una rama la aplicación de las solicitudes de extracción en espera descartadas.                                                                                    |
+| `update_signature_requirement_enforcement_level (actualizar nivel de aplicación del requisito de firma)`                    | Se activa cuando se actualiza la aplicación de la firma de confirmación requerida en una rama.                                                                                                     |
+| `update_pull_request_reviews_enforcement_level (actualizar nivel de aplicación de revisiones de solicitudes de extracción)` | Se activa cuando se actualiza el cumplimiento de las revisiones de solicitudes de extracción requeridas en una rama. Puede ser una de entre `0`(desactivado), `1`(no adminsitradores), `2`(todos). |
+| `update_required_status_checks_enforcement_level (actualizar nivel de aplicación de verificaciones de estado requeridas)`   | Se activa cuando se actualiza en una rama la aplicación de verificaciones de estado requeridas.                                                                                                    |
+| `update_strict_required_status_checks_policy`                                                                               | Se activa cuando se cambia el requisito para que una rama se encuentre actualizada antes de la fusión.                                                                                             |
+| `rejected_ref_update (actualización de referencia rechazada)`                                                               | Se activa cuando se rechaza el intento de actualización de una rama.                                                                                                                               |
+| `policy_override (anulación de política)`                                                                                   | Se activa cuando un administrador del repositorio invalida un requisito de protección de la rama. {% ifversion fpt or ghes or ghae or ghec %}
+| `update_allow_force_pushes_enforcement_level`                                                                               | Se activa cuando se habilitan o inhabilitan las subidas de información forzadas en una rama protegida.                                                                                             |
+| `update_allow_deletions_enforcement_level`                                                                                  | Se activa cuando se habilita o inhabilita el borrado de ramas en una rama protegida.                                                                                                               |
+| `update_linear_history_requirement_enforcement_level`                                                                       | Se activa cuando se habilita o inhabilita el historial de confirmaciones linear requerido para una rama protegida.                                                                                 |
+{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+
+### Acciones de la categoría `pull_request`
+
+| Acción                  | Descripción                                                                                                                       |
+| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`        | Se activa cuando se crea una solicitud de cambios.                                                                                |
+| `close`                 | Se activa cuando se cierra una solicitud de cambios sin haberse fusionado.                                                        |
+| `reopen`                | Se activa cuando se vuelve a abrir una solicitud de cambios después de haberse cerrado previamente.                               |
+| `fusionar`              | Se activa cuando se fusiona una solicitud de cambios.                                                                             |
+| `indirect_merge`        | Se activa cuando una solicitud de cambios se considera como fusionada porque sus confirmaciones se fusionaron en la rama destino. |
+| `ready_for_review`      | Se activa cuando una solicitud de cambios se marca como lista para revisión.                                                      |
+| `converted_to_draft`    | Se activa cuando una solicitud de cambios se convierte en borrador.                                                               |
+| `create_review_request` | Se activa cuando se solicita una revisión.                                                                                        |
+| `remove_review_request` | Se activa cuando se elimina una solicitud de revisión.                                                                            |
+
+### Acciones de la categoría `pull_request_review`
+
+| Acción      | Descripción                                |
+| ----------- | ------------------------------------------ |
+| `enviar`    | Se activa cuando se envía una revisión.    |
+| `descartar` | Se activa cuando se descarta una revisión. |
+| `delete`    | Se activa cuando se borra una revisión.    |
+
+### Acciones de la categoría `pull_request_review_comment`
+
+| Acción           | Descripción                                           |
+| ---------------- | ----------------------------------------------------- |
+| `create (crear)` | Se activa cuando se agrega un comentario de revisión. |
+| `actualización`  | Se activa cuando se cambia un comentario de revisión. |
+| `delete`         | Se activa cuando se borra un comentario de revisión.  |
+
+{% endif %}
+
+### acciones de la categoría `repo`
+
+| Acción                                                                                  | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access (acceder)`                                                                      | Se activa cuando un usuario [cambia la visibilidad](/github/administering-a-repository/setting-repository-visibility) de un repositorio en la organización.                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `actions_enabled`                                                                       | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no se incluye cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)".                                                                                                                                                                                                                                               |
+| `add_member (agregar miembro)`                                                          | Se activa cuando un usuario acepta una [invitación para tener acceso de colaboración a un repositorio](/articles/inviting-collaborators-to-a-personal-repository).                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `add_topic (agregar tema)`                                                              | Se activa cuando un administrador de repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_disabled`                                                            | Se activa cuando un adminsitrador de repositorio inhabilita las características de {% data variables.product.prodname_GH_advanced_security %} en este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".                                                                                                                                                                                            |
+| `advanced_security_enabled`                                                             | Se activa cuando un administrador de repositorio habilita las características de la {% data variables.product.prodname_GH_advanced_security %} para este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+| `archived (archivado)`                                                                  | Se activa cuando un administrador del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público.                                                                                                                                                                                                                                                                                                                                                                                 |
+| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)`       | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público.                                                                                                                                                                                                                                                                                                                                                                                   |
+| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)`          | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).                                                                                                                                                                                                                                                                                                                                                           |
+| `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)`     | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create (crear)`                                                                        | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                                                                 | Se crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".{% endif %}
+| `destroy (destruir)`                                                                    | Se activa cuando [se elimina un repositorio](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `inhabilitar`                                                                           | Se activa cuando se inhabilita un repositorio (p. ej., por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}
+| `habilitar`                                                                             | Se activa cuando se vuelve a habilitar un repositorio.{% ifversion fpt or ghes or ghec %}
+| `remove_actions_secret`                                                                 | Se activa cuando se elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %}
+| `remove_member (eliminar miembro)`                                                      | Se activa cuando un usuario se [elimina de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository).                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `register_self_hosted_runner`                                                           | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)".                                                                                                                                                                                                                                                                                                   |
+| `remove_self_hosted_runner`                                                             | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)".                                                                                                                                                                                                                                                                                                                         |
+| `remove_topic (eliminar tema)`                                                          | Se activa cuando un administrador del repositorio elimina un tema de un repositorio.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `rename (renombrar)`                                                                    | Se activa cuando [se vuelve a nombrar a un repositorio](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`                                                             | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                                                                          |
+| `self_hosted_runner_offline`                                                            | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Verificar el estado de un ejecutor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`                                                            | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy`                                                  | Se activa cuando se cambia la configuración para requerir aprobaciones para los flujos de trabajo de las bifurcaciones públicas. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)".{% endif %}
+| `set_actions_retention_limit`                                                           | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Administrar la configuración de {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`                                                          | Se activa cuando se cambia la política para flujos de trabajo en las bifurcaciones de los repositorios privados. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %}
+| `transferencia`                                                                         | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `transfer_start (comienzo de transferencia)`                                            | Se activa cuando está por ocurrir una transferencia de repositorio.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `unarchived (desarchivado)`                                                             | Se activa cuando un administrador de repositorio deja de archivar un repositorio.{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                                                                 | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### acciones de la categoría `repository_advisory`
+
+| Acción             | Descripción                                                                                                                                                                                                                                                                        |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `close`            | Se activa cuando alguien cierra una asesoría de seguridad. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". |
+| `cve_request`      | Se activa cuando alguien solicita un número de CVE (Vulnerabilidades y Exposiciones Comunes) de {% data variables.product.prodname_dotcom %} para un borrador de asesoría de seguridad.                                                                                            |
+| `github_broadcast` | Se activa cuando {% data variables.product.prodname_dotcom %} hace pública una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}.                                                                                                              |
+| `github_withdraw`  | Se activa cuando {% data variables.product.prodname_dotcom %} retira una asesoría de seguridad que se publicó por error.                                                                                                                                                           |
+| `open`             | Se activa cuando alguien abre un borrador de asesoría de seguridad.                                                                                                                                                                                                                |
+| `publish`          | Se activa cuando alguien publica una asesoría de seguridad.                                                                                                                                                                                                                        |
+| `reopen`           | Se activa cuando alguien vuelve a abrir un borrador de asesoría de seguridad.                                                                                                                                                                                                      |
+| `actualización`    | Se activa cuando alguien edita un borrador de asesoría de seguridad o una asesoría de seguridad publicada.                                                                                                                                                                         |
+
+### Acciones de la categoría `repository_content_analysis`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                      |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `habilitar`   | Se activa cuando un propietario de la organización o persona con acceso administrativo al repositorio [habilita la configuración de uso de datos para un repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).            |
+| `inhabilitar` | Se habilita cuando un propietario de la organización o una persona con acceso administrativo en el repositorio [inhabilita la configuración de uso de datos para un repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). |
+
+{% endif %}{% ifversion fpt or ghec %}
+
+### Acciones de la categoría `repository_dependency_graph`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo en este inhabilita la gráfica de dependencias para un repositorio {% ifversion fpt or ghec %}privado {% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". |
+| `habilitar`   | Se activa cuando un propietario del repositorio o persona con acceso administrativo en el mismo habilita la gráfica de dependencias para un repositorio {% ifversion fpt or ghec %}privado {% endif %}.                                                                                                                                                                       |
+
+{% endif %}{% ifversion ghec or ghes or ghae %}
+### Acciones de la categoría `repository_secret_scanning`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                                       |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de repositorio o persona con acceso administrativo a este inhabilita el escaneo de secretos para un repositorio {% ifversion ghec %}privado o interno{% endif %}. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |
+| `habilitar`   | Se activa cuando un propietario de repositorio o persona con acceso administrativo a este habilita el escaneo de secretos para un repositorio {% ifversion ghec %}privado o interno{% endif %}.                                                                                                                                                   |
+
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+### acciones de la categoría `repository_vulnerability_alert`
+
+| Acción           | Descripción                                                                                                                                                                                                                                                                                                                                                                                      |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create (crear)` | Se activa cuando {% data variables.product.product_name %} crea una alerta del {% data variables.product.prodname_dependabot %} para un repositorio que utiliza una dependencia vulnerable. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". |
+| `descartar`      | Se activa cuando un propietario de organización o persona con acceso administrativo al repositorio descarta una alerta del {% data variables.product.prodname_dependabot %} sobre una dependencia vulnerable.                                                                                                                                                                                    |
+| `resolver`       | Se activa cuando alguien con acceso de escritura en un repositorio sube cambios para actualizar y resolver una vulnerabilidad en una dependencia de proyecto.                                                                                                                                                                                                                                    |
+
+{% endif %}{% ifversion fpt or ghec %}
+### acciones de la categoría `repository_vulnerability_alerts`
+
+| Acción                   | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `authorized_users_teams` | Se activa cuando un propietario de la organización o un miembro con permisos de administrador en el repositorio actualiza la lista de personas o equipos autorizados para recibir las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en dicho repositorio. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". |
+| `inhabilitar`            | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este inhabilita las {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `habilitar`              | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este habilita las {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+{% endif %}{% ifversion ghec %}
+### Acciones de la categoría `role`
+| Acción               | Descripción                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`     | Se activa cuando un propietario de una organización crea un rol de repositorio personalizado nuevo. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".      |
+| `destroy (destruir)` | Se activa cuando el propietario de una organización borra un rol de repositorio personalizado. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".           |
+| `actualización`      | Se activa cuando un propietario de una organización edita un rol de repositorio personalizado existente. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)". |
+
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+### Acciones de la categoría `secret_scanning`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                                      |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando el propietario de una organización inhabilita el escaneo de secretos para todos los repositorios{% ifversion ghec %} privados o internos{% endif %} existentes. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |
+| `habilitar`   | Se activa cuando un propietario de organización habilita el escaneo de secretos para todos los repositorios {% ifversion ghec %} privados o internos{% endif %} existentes.                                                                                                                                                      |
+
+### Acciones de la categoría `secret_scanning_new_repos`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                                                                              |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `inhabilitar` | Se activa cuando un propietario de organización inhabilita el escaneo de secretos para todos los repositorios {% ifversion ghec %}privados o internos {% endif %}nuevos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |
+| `habilitar`   | Se activa cuando un propietario de organización habilita el escaneo de secretos para todos los repositorios {% ifversion ghec %}privados o internos {% endif %}nuevos.                                                                                                                                                   |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### acciones de la categoría `sponsors`
+
+| Acción                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`                                                                                   | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                           |
+| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)`                 | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                               |
+| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)`                                        | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                            |
+| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)`                                          | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                   |
+| `sponsor_sponsorship_payment_complete`                                                                            | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                      |
+| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)`                     | Se activa cuando cambias si quieres recibir actualizaciones de una cuenta patrocinada por correo electrónico (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                               |
+| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)`                                   | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                |
+| `sponsored_developer_approve (aprobación de programador patrocinado)`                                             | Se activa cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                              |
+| `sponsored_developer_create (creación de programador patrocinado)`                                                | Se activa cuando se crea la cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                |
+| `sponsored_developer_disable`                                                                                     | Se activa cuando se inhabilita tu cuenta de {% data variables.product.prodname_sponsors %}
+| `sponsored_developer_redraft`                                                                                     | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado                                                                                                                                                                                               |
+| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)`                        | Se activa cuando editas tu perfil de organización patrocinada (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                    |
+| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)`                       | Se activa cuando emites tu solicitud para {% data variables.product.prodname_sponsors %} para su aprobación (consulta la sección "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")        |
+| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                             |
+| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)`      | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                        |
+| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)`             | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `waitlist_join (incorporación a la lista de espera)`                                                              | Se activa cuando te unes a la lista de espera para convertirte en una organización patrocinada (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                       |
+{% endif %}
+
+### acciones de la categoría `team`
+
+| Acción                                      | Descripción                                                                                                                                                                                                                                                                          |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `add_member (agregar miembro)`              | Se activa cuando un miembro de una organización se [agrega a un equipo](/articles/adding-organization-members-to-a-team).                                                                                                                                                            |
+| `add_repository (agregar repositorio)`      | Se activa cuando se le otorga el control de un repositorio a un equipo.                                                                                                                                                                                                              |
+| `change_parent_team (cambiar equipo padre)` | Se activa cuando se crea un equipo hijo o [se modifica el padre de un equipo hijo](/articles/moving-a-team-in-your-organization-s-hierarchy).                                                                                                                                        |
+| `change_privacy (cambiar privacidad)`       | Se activa cuando se modifica el nivel de privacidad de un equipo.                                                                                                                                                                                                                    |
+| `create (crear)`                            | Se activa cuando se crea un equipo nuevo.                                                                                                                                                                                                                                            |
+| `demote_maintainer`                         | Se activa cuando se baja de categoría a un usuario de mantenedor de equipo a miembro de equipo. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." |
+| `destroy (destruir)`                        | Se activa cuando se elimina un equipo de la organización.                                                                                                                                                                                                                            |
+| `team.promote_maintainer`                   | Se activa cuando se promueve a un usuario de miembro de equipo a mantenedor de equipo. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."          |
+| `remove_member (eliminar miembro)`          | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team).                                                                                                                                                      |
+| `remove_repository (eliminar repositorio)`  | Se activa cuando un repositorio deja de estar bajo el control de un equipo.                                                                                                                                                                                                          |
+
+### acciones de la categoría `team_discussions`
+
+| Acción        | Descripción                                                                                                                                                                                                                                                               |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inhabilitar` | Se activa cuando un propietario de la organización inhabilita los debates de equipo para una organización. Para obtener más información, consulta "[Desactivar los debates del equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)". |
+| `habilitar`   | Se activa cuando un propietario de la organización habilita los debates de equipo para una organización.                                                                                                                                                                  |
+
+{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### Acciones de la categoría `workflows`
+
+{% data reusables.actions.actions-audit-events-workflow %}
+{% endif %}
+## Leer más
+
+- "[Mantener tu organización segura](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+- "[Exportar la información de miembro para tu organización](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
new file mode 100644
index 0000000000..9b7a3176c5
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -0,0 +1,31 @@
+---
+title: Revisar las integraciones instaladas de tu organización
+intro: Puedes revisar los niveles de permiso para las integraciones instaladas de tu organización y configurar cada accedo de integración a los repositorios de la organización.
+redirect_from:
+  - /articles/reviewing-your-organization-s-installed-integrations
+  - /articles/reviewing-your-organizations-installed-integrations
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations
+  - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Revisar las integraciones instaladas
+---
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
+{% elsif ghae or ghes < 3.4 %}
+1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %} Instaladas**. ![Pestaña de {% data variables.product.prodname_github_apps %} instaladas en la barra lateral de parámetros de la organización](/assets/images/help/organizations/org-settings-installed-github-apps.png)
+{% endif %}
+2. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). ![Botón Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png)
+6. Revisa el acceso al repositorio y los permisos de {% data variables.product.prodname_github_app %}. ![Opción para darle acceso a {% data variables.product.prodname_github_app %} a todos los repositorios o a repositorios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png)
+    - Para darle acceso a la {% data variables.product.prodname_github_app %} a todos los repositorios de tu organización, selecciona **All repositories** (Todos los repositorios).
+    - Para elegir repositorios específicos para darle acceso a la aplicación, selecciona **Only select repositories** (Solo repositorios seleccionados), luego escribe el nombre de un repositorio.
+7. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
new file mode 100644
index 0000000000..df495a0d4f
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -0,0 +1,17 @@
+---
+title: Managing two-factor authentication for your organization
+shortTitle: Manage 2FA
+intro: You can view whether users with access to your organization have two-factor authentication (2FA) enabled and require 2FA.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /preparing-to-require-two-factor-authentication-in-your-organization
+  - /requiring-two-factor-authentication-in-your-organization
+---
+
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..d1c6211013
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: Prepararse para requerir autenticación de dos factores en tu organización
+intro: 'Antes de requerir la autenticación de dos factores (2FA), puedes notificar a los usuarios acerca del futuro cambio y verificar quien ya utiliza 2FA.'
+redirect_from:
+  - /articles/preparing-to-require-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Prepararse para requerir 2FA
+---
+
+Recomendamos que notifiques a {% ifversion fpt or ghec %}los miembros de la organización, a los colaboradores externos y a los gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} por lo menos una semana antes de requerir 2FA en tu organización.
+
+Cuando solicitas que se use la autenticación de dos factores para tu organización, los miembros, los colaboradores externos y los gerentes de facturación (incluidas las cuentas bot) que no utilizan 2FA se eliminarán de tu organización y perderán acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización.
+
+Antes de solicitar 2FA en tu organización, recomendamos que:
+  - [Habilites 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) en tu cuenta personal
+  - Le solicites a las personas en tu organización que configuren 2FA en sus cuentas
+  - Consultes si [los usuarios en tu organizacipon tienen habilitado el 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/)
+  - Le adviertas a los usuarios que una vez que el 2FA esté habilitado, aquellos sin 2FA se eliminarán automáticamente de la organización
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..46e042b8c4
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Solicitar autenticación de dos factores en tu organización
+intro: 'Los propietarios de la organización pueden requerir que los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} habiliten la autenticación de dos factores para sus cuentas personales, lo que hace que sea más complicado para los actores maliciosos acceder a los repositorios y parámetros de una organización.'
+redirect_from:
+  - /articles/requiring-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Requerir 2FA
+---
+
+## Acerca de la autenticación bifactorial para las organizaciones
+
+{% data reusables.two_fa.about-2fa %} Puedes requerir que todos los {% ifversion fpt or ghec %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} en tu organización habiliten la autenticación bifactorial en {% data variables.product.product_name %}. Para obtener más información acerca de la autenticación bifactorial, consulta la sección "[Asegurar tu cuenta con la autenticación bifactorial (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
+
+{% ifversion fpt or ghec %}
+
+También puedes requerir autenticación bifactorial para las organizaciones en una empresa. Para obtener más información, consulta la sección "[Requerir políticas para la configuración de seguridad en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
+
+{% endif %}
+
+{% warning %}
+
+**Advertencias:**
+
+- Cuando requieres el uso de autenticación de dos factores para tu organización, los {% ifversion fpt or ghec %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} (incluidas las cuentas de bot) que no utilicen la 2FA se eliminarán de la organización y perderán el acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes [reinstalar sus privilegios y parámetros de acceso](/articles/reinstating-a-former-member-of-your-organization) si habilitan la autenticación de dos factores para su cuenta personal en el transcurso de los tres meses posteriores a la eliminación desde tu organización.
+- Si un propietario de la organización, miembro,{% ifversion fpt or ghec %} gerente de facturación{% endif %} o colaborador externo inhabilita la 2FA para su cuenta personal después de que hayas habilitado la autenticación de dos factores requerida, se lo eliminará automáticamente de la organización.
+- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización.
+
+{% endwarning %}
+
+{% data reusables.two_fa.auth_methods_2fa %}
+
+## Prerrequisitos
+
+Antes de que requieras que los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} utilicen la autenticación bifactorial, debes habilitarla para tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta "[Proteger tu cuenta con la autenticación de dos factores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
+
+Antes de que requieras el uso de autenticación de dos factores, recomendamos que se lo notifiques a los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} y les solicites que configuren la 2FA para sus cuentas. Puedes ver si los miembros y colaboradores externos ya utilizan la 2FA. Para obtener más información, consulta "[Ver si los usuarios en tu organización tienen la 2FA habilitada](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)".
+
+## Solicitar autenticación de dos factores en tu organización
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+{% ifversion fpt or ghec %}
+8. Si algún miembro o colaborador externo se elimina de tu organización, te recomendamos enviarle una invitación para reinstalar sus privilegios antiguos y el acceso a tu organización. Deben habilitar la autenticación de dos factores para poder aceptar la invitación.
+{% endif %}
+
+## Ver las personas que se eliminaron de tu organización
+
+Para ver las personas que se eliminaron automáticamente de tu organización por no cumplir cuando les requeriste la autenticación de dos factores, puedes [buscar el registro de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) para las personas eliminadas de tu organización. El evento de registro de auditoría mostrará si se eliminó a una persona por no cumplir con la 2FA.
+
+![Evento de registro de auditoría que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+4. Ingresa tu consulta de búsqueda. Para buscar por:
+    - Miembros de la organización eliminados, utiliza `action:org.remove_member` en tu consulta de búsqueda
+    - Colaboradores externos eliminados, utiliza `action:org.remove_outside_collaborator` en tu consulta de búsqueda{% ifversion fpt or ghec %}
+    - Gerentes de facturación eliminados, utiliza `action:org.remove_billing_manager`en tu consulta de búsqueda{% endif %}
+
+ También puedes ver las personas que se eliminaron de tu organización utilizando un [período de tiempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) en tu búsqueda.
+
+## Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización
+
+Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización.
+
+## Leer más
+
+- "[Ver si los usuarios de tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Proteger tu cuenta con autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Reinstalar un miembro antiguo de tu organización](/articles/reinstating-a-former-member-of-your-organization)"
+- "[Reinstalar el acceso a tu organización de un colaborador externo antiguo](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
new file mode 100644
index 0000000000..ccdd8a7ce3
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -0,0 +1,33 @@
+---
+title: Ver si los usuarios en tu organización han habilitado 2FA
+intro: 'Puedes ver los propietarios de la organización, miembros y colaboradores externos que han habilitado la autenticación de dos factores.'
+redirect_from:
+  - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View 2FA usage
+---
+
+{% note %}
+
+**Nota:** puedes solicitar que todos los miembros {% ifversion fpt or ghec %}, incluidos, los propietarios, gerentes de facturación y{% else %} y{% endif %} colaboradores externos en tu organización tengan habilitada la autenticación de dos factores. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. Para ver los miembros de la organización, incluidos los propietarios de la organización, que han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png)
+5. Para ver los colaboradores externos en tu organización, dentro de la pestaña "People" (Personas), haz clic en **Outside collaborators (Colaboradores externos)**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png)
+6. Para ver qué colaboradores externos han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
+
+## Leer más
+
+- "[Ver los roles de las personas en un organización](/articles/viewing-people-s-roles-in-an-organization)"
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 841dca73ea..134d90e67d 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -23,6 +23,7 @@ If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index f7caf78b8b..f88cd1dba9 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -90,6 +90,8 @@ You can only choose an additional permission if it's not already included in the
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
 - **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts.
+- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}.
+- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}.
 - **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts.
 
diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index df0ef33659..81b5d7e548 100644
--- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -23,8 +23,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
 ## Verifying a domain for your user site
 
 {% data reusables.user_settings.access_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
@@ -38,8 +37,7 @@ Organization owners can verify custom domains for their organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index 225c6dbf6e..fe14aac772 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -170,6 +170,7 @@ For more information on creating pull requests in {% data variables.product.prod
 ## Further reading
 
 - "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)"
 - "[Changing the base branch of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)"
 - "[Adding issues and pull requests to a project board from the sidebar](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)"
 - "[About automation for issues and pull requests with query parameters](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 6a5e87fe5c..7aed20a9ce 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -22,6 +22,7 @@ children:
   - /using-query-parameters-to-create-a-pull-request
   - /changing-the-stage-of-a-pull-request
   - /requesting-a-pull-request-review
+  - /keeping-your-pull-request-in-sync-with-the-base-branch
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
 shortTitle: Propose changes
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
new file mode 100644
index 0000000000..c329dc48f2
--- /dev/null
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
@@ -0,0 +1,53 @@
+---
+title: Keeping your pull request in sync with the base branch
+intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.'
+permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Update the head branch
+---
+
+## About keeping your pull request in sync
+
+Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging.
+
+You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true:
+
+* There are no merge conflicts between the pull request branch and the base branch.
+* The pull request branch is not up to date with the base branch.
+* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} or the setting to always suggest updating branches is enabled{% endif %}.
+
+For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}" and "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}."
+
+If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)."
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created.
+{% else %}
+Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request.
+{% endif %}
+
+## Updating your pull request branch
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull requests" list, click the pull request you'd like to update.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+1. In the merge section near the bottom of the page, you can:
+   - Click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png)
+   - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch. ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png)
+{% else %}
+1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch.png)
+{% endif %}
+
+## Leer más
+
+- "[Acerca de las solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)"
+- "[Confirmar cambios en una rama de la solicitud de extracción creada desde una bifurcación](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
index b8b6a958b1..3a4ac61951 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
@@ -19,4 +19,4 @@ shortTitle: Configurar el rebase de confirmaciones
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de rebase). Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base. Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base. Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png)
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index 174f9b028d..eac9f7a42c 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -20,9 +20,9 @@ shortTitle: Configure commit squashing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Merge button", optionally select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.
 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. Under "Merge button", select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. If you select another merge method besides **Allow squash merging**, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
+4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. If you select another merge method besides **Allow squash merging**, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
 ![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png)
 
 ## Further reading
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
index 32332a5346..f2025f2b68 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -16,6 +16,7 @@ children:
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
   - /using-a-merge-queue
+  - /managing-suggestions-to-update-pull-request-branches
   - /managing-auto-merge-for-pull-requests-in-your-repository
   - /managing-the-automatic-deletion-of-branches
 shortTitle: Configurar fusiones de solicitudes de cambio
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 1b863c2771..3d7b5e9377 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -25,5 +25,5 @@ If you allow auto-merge for pull requests in your repository, people with write
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under "Merge button", select or deselect **Allow auto-merge**.
+1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**.
   ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
new file mode 100644
index 0000000000..a724a1302b
--- /dev/null
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -0,0 +1,23 @@
+---
+title: Managing suggestions to update pull request branches
+intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+versions:
+  fpt: '*'
+  ghes: '> 3.4'
+  ghae: issue-6069
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage branch updates
+permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
+---
+
+## About suggestions to update a pull request branch
+
+If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+## Managing suggestions to update a pull request branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**. ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
index 3c7a8eee83..19ee680be0 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
@@ -18,7 +18,7 @@ Anyone with admin permissions to a repository can enable or disable the automati
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Merge button", select or unselect **Automatically delete head branches**.
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or unselect **Automatically delete head branches**.
   ![Checkbox to enable or disable automatic deletion of branches](/assets/images/help/repository/automatically-delete-branches.png)
 
 ## Further reading
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 32934b1829..24e24db8c6 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -52,7 +52,8 @@ Cuando transfieres un repositorio, también se transfieren sus propuestas, solic
   $ git remote set-url origin <em>new_url</em>
   ```
 
-- Cuando transfieres un repositorio desde una organización a una cuenta de usuario, los colaboradores de solo lectura de este no se transferirán. Esto es porque los colaboradores no pueden tener acceso de solo lectura a los repositorios que pertenecen a una cuenta de usuario. Para obtener más información acerca de los niveles de permiso en los repositorios, consulta las secciones "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y"[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
+- Cuando transfieres un repositorio desde una organización a una cuenta de usuario, los colaboradores de solo lectura de este no se transferirán. Esto es porque los colaboradores no pueden tener acceso de solo lectura a los repositorios que pertenecen a una cuenta de usuario. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
+- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
 Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)."
 
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index d5d45325ef..d6ac9ce97e 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -50,6 +50,8 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to
 A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
 
 If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
+
+CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 ### Example of a CODEOWNERS file
 ```
 # This is a comment.
@@ -97,6 +99,10 @@ apps/ @octocat
 # subdirectories.
 /docs/ @doctocat
 
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
 # In this example, @octocat owns any file in the `/apps` 
 # directory in the root of your repository except for the `/apps/github` 
 # subdirectory, as its owners are left empty.
@@ -112,21 +118,6 @@ There are some syntax rules for gitignore files that do not work in CODEOWNERS f
 ## CODEOWNERS and branch protection
 Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." 
 
-### Example of a CODEOWNERS file
-```
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat.
-/apps/ @doctocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat or @octocat.
-/apps/ @doctocat @octocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from a member of the @example-org/content team.
-/apps/ @example-org/content-team
-```
-
 
 ## Further reading
 
diff --git a/translations/es-ES/content/rest/guides/delivering-deployments.md b/translations/es-ES/content/rest/guides/delivering-deployments.md
index 870e7e2465..84c2320a2a 100644
--- a/translations/es-ES/content/rest/guides/delivering-deployments.md
+++ b/translations/es-ES/content/rest/guides/delivering-deployments.md
@@ -20,7 +20,7 @@ La [API de despliegues][deploy API] proporciona a tus proyectos hospedados en {%
 
 Esta guía utilizará la API para demostrar una configuración que puedes utilizar. En nuestro escenario, nosotros:
 
-* Fusionamos una solicitud de extracción
+* Merge a pull request.
 * Cuando finaliza la IC, configuramos el estado de la solicitud de extracción según corresponda.
 * Cuando se fusiona la solicitud de extracción, ejecutamos nuestro despliegue en nuestro servidor.
 
diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
index a070a5016b..1e51b48abf 100644
--- a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
@@ -42,9 +42,9 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > Content-Type: application/json; charset=utf-8
 > ETag: "a00049ba79152d03380c34652f2cb612"
 > X-GitHub-Media-Type: github.v3
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4987
-> X-RateLimit-Reset: 1350085394{% ifversion ghes %}
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4987
+> x-ratelimit-reset: 1350085394{% ifversion ghes %}
 > X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %}
 > X-GitHub-Enterprise-Version: GitHub AE{% endif %}
 > Content-Length: 5
@@ -366,16 +366,16 @@ Los encabezados HTTP recuperados para cualquier solicitud de la API muestran tu
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 56
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 56
+> x-ratelimit-reset: 1372700873
 ```
 
 | Nombre del Encabezado   | Descripción                                                                                                                                          |
 | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `X-RateLimit-Limit`     | La cantidad máxima de solicitudes que puedes hacer por hora.                                                                                         |
-| `X-RateLimit-Remaining` | La cantidad de solicitudes que quedan en la ventana de límite de tasa actual.                                                                        |
-| `X-RateLimit-Reset`     | La hora en la que se restablecerá la ventana de límite de tasa actual en [segundos de tiempo satelital UTC](http://en.wikipedia.org/wiki/Unix_time). |
+| `x-ratelimit-limit`     | La cantidad máxima de solicitudes que puedes hacer por hora.                                                                                         |
+| `x-ratelimit-remaining` | La cantidad de solicitudes que quedan en la ventana de límite de tasa actual.                                                                        |
+| `x-ratelimit-reset`     | La hora en la que se restablecerá la ventana de límite de tasa actual en [segundos de tiempo satelital UTC](http://en.wikipedia.org/wiki/Unix_time). |
 
 Si necesitas ver la hora en un formato diferente, cualquier lenguaje de programación moderno puede ayudarte con esta tarea. Por ejemplo, si abres la consola en tu buscador web, puedes obtener fácilmente el tiempo de restablecimiento como un objeto de Tiempo de JavaScript.
 
@@ -389,9 +389,9 @@ Si excedes el límite de tasa, se regresará una respuesta de error:
 ```shell
 > HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 0
-> X-RateLimit-Reset: 1377013266
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 0
+> x-ratelimit-reset: 1377013266
 
 > {
 >    "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
@@ -407,9 +407,9 @@ If your OAuth App needs to make unauthenticated calls with a higher rate limit,
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4966
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4966
+> x-ratelimit-reset: 1372700873
 ```
 
 {% note %}
@@ -489,9 +489,9 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
 > HTTP/2 304
@@ -499,18 +499,18 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
 > HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 ```
 
 ## Intercambio de recursos de origen cruzado
@@ -523,7 +523,7 @@ Aquí hay una solicitud de ejemplo que se envió desde una consulta de buscador
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
 HTTP/2 302
 Access-Control-Allow-Origin: *
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
 
 Así se ve una solicitud de prevuelo de CORS:
@@ -534,7 +534,7 @@ HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 Access-Control-Max-Age: 86400
 ```
 
@@ -548,9 +548,9 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > /**/foo({
 >   "meta": {
 >     "status": 200,
->     "X-RateLimit-Limit": "5000",
->     "X-RateLimit-Remaining": "4966",
->     "X-RateLimit-Reset": "1372700873",
+>     "x-ratelimit-limit": "5000",
+>     "x-ratelimit-remaining": "4966",
+>     "x-ratelimit-reset": "1372700873",
 >     "Link": [ // pagination headers and other links
 >       ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}]
 >     ]
@@ -652,3 +652,4 @@ Si los pasos anteriores no dan como resultado ninguna información, utilizaremos
 [uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
+
diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md
index 4793bffc9f..ab9cbd2350 100644
--- a/translations/es-ES/content/rest/reference/scim.md
+++ b/translations/es-ES/content/rest/reference/scim.md
@@ -33,15 +33,15 @@ Debes autenticarte como un propietario de una organización de {% data variables
 
 ### Atributos de Usuario de SCIM compatibles
 
-| Nombre           | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| ---------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName`       | `secuencia` | El nombre de usuario para el usuario.                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `name.givenName` | `secuencia` | El primer nombre del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| `name.lastName`  | `secuencia` | El apellido del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| `emails`         | `arreglo`   | Lista de correos electrónicos del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| `externalId`     | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. |
-| `id`             | `secuencia` | Identificador que genera la terminal de SCIM de GitHub.                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `active`         | `boolean`   | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false).                                                                                                                                                                                                                                                                                                                                                                   |
+| Nombre            | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ----------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName`        | `secuencia` | El nombre de usuario para el usuario.                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `name.givenName`  | `secuencia` | El primer nombre del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `name.familyName` | `secuencia` | El apellido del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `emails`          | `arreglo`   | Lista de correos electrónicos del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `externalId`      | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. |
+| `id`              | `secuencia` | Identificador que genera la terminal de SCIM de GitHub.                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `active`          | `boolean`   | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false).                                                                                                                                                                                                                                                                                                                                                                   |
 
 {% note %}
 
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
index cce69895f4..0ca51a8f75 100644
--- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -49,6 +49,43 @@ shortTitle: Administrar los niveles de pago
 {% data reusables.sponsors.tier-update %}
 {% data reusables.sponsors.retire-tier %}
 
+## Adding a repository to a sponsorship tier
+
+{% data reusables.sponsors.sponsors-only-repos %}
+
+### About adding repositories to a sponsorship tier
+
+To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository.
+
+When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled.
+
+Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier.
+
+You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync.
+
+### About transfers for repositories that are added to sponsorship tiers
+
+If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected.
+
+- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors.
+- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository.
+- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository.
+
+### Adding a repository a sponsorship tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+1. Select **Grant sponsors access to a private repository**.
+
+   ![Screenshot of checkbox to grant sponsors access to a private repository](/assets/images/help/sponsors/grant-sponsors-access-to-repo-checkbox.png)
+
+1. Select the dropdown menu and click the repository you want to add.
+
+   ![Screenshot of dropdown menu to choose the repository to grant sponsors access to](/assets/images/help/sponsors/grant-sponsors-access-to-repo-dropdown.png)
+
+{% data reusables.sponsors.tier-update %}
+
 ## Habilitar niveles con cantidades personalizadas
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
diff --git a/translations/es-ES/data/features/code-scanning-task-lists.yml b/translations/es-ES/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..0de30490f7
--- /dev/null
+++ b/translations/es-ES/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/translations/es-ES/data/features/codeql-ml-queries.yml b/translations/es-ES/data/features/codeql-ml-queries.yml
new file mode 100644
index 0000000000..c74f86b77f
--- /dev/null
+++ b/translations/es-ES/data/features/codeql-ml-queries.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5604.
+#Documentation for the beta release of CodeQL queries boosted by machine learning
+#to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/es-ES/data/product-examples/README.md b/translations/es-ES/data/product-examples/README.md
index 7764a2e7bb..4fbf18eafc 100644
--- a/translations/es-ES/data/product-examples/README.md
+++ b/translations/es-ES/data/product-examples/README.md
@@ -2,7 +2,7 @@
 
 Las páginas que utilizan el diseño de `product-landing` podrían incluir una sección de `Examples` opcionalmente. Actualmente, tenemos compatibilidad con tres tipos de ejemplos:
 
-1. Ejemplos de código Consulta https://docs.github.com/en/actions#code-examples.
+1. Ejemplos de código Consulta https://docs.github.com/en/codespaces#code-examples.
 
 2. Ejemplos de comunidad Consulta https://docs.github.com/en/discussions#community-examples.
 
@@ -10,7 +10,7 @@ Las páginas que utilizan el diseño de `product-landing` podrían incluir una s
 
 ## Cómo funciona
 
-Los datos de ejemplo de cada producto se definen en `data/product-landing-examples`, en un subdirectorio que obtiene su nombre para el **producto** y un archivo YML que obtiene su nombre para el **tipo de ejemplo** (por ejemplo: `data/product-examples/sponsors/user-examples.yml` o `data/product-examples/actions/code-examples.yml`). Actualmente solo tenemos compatibilidad con un tipo de ejemplo por producto.
+Example data for each product is defined in `data/product-landing-examples`, in a subdirectory named for the **product** and a YML file named for the **example type** (e.g., `data/product-examples/sponsors/user-examples.yml` or `data/product-examples/codespaces/code-examples.yml`). Actualmente solo tenemos compatibilidad con un tipo de ejemplo por producto.
 
 ### Control de versiones
 
diff --git a/translations/es-ES/data/product-examples/actions/code-examples.yml b/translations/es-ES/data/product-examples/actions/code-examples.yml
deleted file mode 100644
index 78a33083dd..0000000000
--- a/translations/es-ES/data/product-examples/actions/code-examples.yml
+++ /dev/null
@@ -1,335 +0,0 @@
----
-- 
-  title: Servicios de ejemplo
-  description: Flujos de trabajo de ejemplo que utilizan contenedores de servicio
-  languages: JavaScript
-  href: actions/example-services
-  tags:
-    - contenedores de servicio
-- 
-  title: Configurar las etiquetas de GitHub de forma declaratoria
-  description: Acción de GitHub para configurar las etiquetas de forma declaratoria a través de los repositorios
-  languages: JavaScript
-  href: lannonbr/issue-label-manager-action
-  tags:
-    - propuestas
-    - etiquetas
-- 
-  title: Sincronizar las etiquetas de GitHub de forma declaratoria
-  description: Acción de GitHub para sincronizar las etiquetas de GitHub en la forma declaratoria
-  languages: 'Go, Dockerfile'
-  href: micnncim/action-label-syncer
-  tags:
-    - propuestas
-    - etiquetas
-- 
-  title: Agregar lanzamientos a GitHub
-  description: Publicar lanzamientos de GitHub en una acción
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Github-Release-Action
-  tags:
-    - releases
-    - publicar
-- 
-  title: Publicar una imagen de docker en Dockerhub
-  description: Una GitHub Action que se utiliza para crear y publicar imágenes de Docker
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Publish-Docker-Github-Action
-  tags:
-    - docker
-    - publicar
-    - build
-- 
-  title: Crear una propuesta utilizando el contenido de un archivo
-  description: Una acción de GitHub para crear una propuesta utilizando el contenido de un archivo
-  languages: 'JavaScript, Python'
-  href: peter-evans/create-issue-from-file
-  tags:
-    - propuestas
-- 
-  title: Publicar Lanzamientos de GitHub con Activos
-  description: Acción de GitHub para crear Lanzamientos de GitHub
-  languages: 'TypeScript, Shell, JavaScript'
-  href: softprops/action-gh-release
-  tags:
-    - releases
-    - publicar
-- 
-  title: GitHub Project Automation+
-  description: Automatizar tarjetas de proyectos de GitHub con cualquier evento de webhook
-  languages: JavaScript
-  href: alex-page/github-project-automation-plus
-  tags:
-    - proyectos
-    - automatización
-    - propuestas
-    - solicitudes de extracción
-- 
-  title: Ejecutar GitHub Actions localmente con una interface web
-  description: Ejecuta flujos de trabajo de GitHub Actions localmente (local)
-  languages: 'JavaScript, HTML, Dockerfile, CSS'
-  href: phishy/wflow
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: Ejecuta tus GitHub Actions localmente
-  description: Ejecuta GitHub Actions localmente en la Terminal
-  languages: 'Go, Shell'
-  href: nektos/act
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: Crea y publica una APK de depuración en Android
-  description: Crea y lanza la APK de depuración desde tu proyecto de Android
-  languages: 'Shell, Dockerfile'
-  href: ShaunLWM/action-release-debugapk
-  tags:
-    - android
-    - build
-- 
-  title: Genera números de compilación secuenciales para GitHub Actions
-  description: Acción de GitHub para generar números de compilación secuenciales.
-  languages: JavaScript
-  href: einaregilsson/build-number
-  tags:
-    - build
-    - automatización
-- 
-  title: Acciones de GitHub para subir de vuelta a un repositorio
-  description: Subir cambios de Git a un repositorio de GitHub sin dificultades de autenticación
-  languages: 'JavaScript, Shell'
-  href: ad-m/github-push-action
-  tags:
-    - publicar
-- 
-  title: Generar notas de lanzamiento en tus eventos
-  description: Acción para autogenerar una nota de lanzamiento que se base en tus eventos
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/release-notes-generator-action
-  tags:
-    - releases
-    - publicar
-- 
-  title: Crear una página de wiki de GitHub en el archivo de markdown proporcionado
-  description: Crear una página de wiki de GitHub en el archivo de markdown proporcionado
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/wiki-page-creator-action
-  tags:
-    - wiki
-    - publicar
-- 
-  title: Etiqueta tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados)
-  description: GitHub Action para etiquetar tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados)
-  languages: 'TypeScript, Dockerfile, JavaScript'
-  href: Decathlon/pull-request-labeler-action
-  tags:
-    - proyectos
-    - propuestas
-    - etiquetas
-- 
-  title: Agregar una etiqueta a tus solicitudes de cambios en nombre del equipo autor
-  description: Acción de GitHub para etiquetar tus solicitudes de cambios con base en el nombre del autor
-  languages: 'TypeScript, JavaScript'
-  href: JulienKode/team-labeler-action
-  tags:
-    - solicitud de cambios
-    - etiquetas
-- 
-  title: Obtén una lista de cambios a los archivos con una PR/Subida
-  description: Esta acción obtendrá y te proporcionará las salidas de los archivos que hayan cambiado en tu repositorio
-  languages: 'TypeScript, Shell, JavaScript'
-  href: trilom/file-changes-action
-  tags:
-    - flujo de trabajo
-    - repositorio
-- 
-  title: Acciones privadas en cualquier flujo de trabajo
-  description: Permite que se reutilicen las GitHub Actions privadas fácilmente
-  languages: 'TypeScript, JavaScript, Shell'
-  href: InVisionApp/private-action-loader
-  tags:
-    - flujo de trabajo
-    - tools
-- 
-  title: Etiqueta tus propuestas utilizando sus contenidos
-  description: Una GitHub Action para etiquetar automáticamente las propuestas con etiquetas y asignados
-  languages: 'JavaScript, TypeScript'
-  href: damccorm/tag-ur-it
-  tags:
-    - flujo de trabajo
-    - tools
-    - etiquetas
-    - propuestas
-- 
-  title: Revertir un lanzamiento de GitHub
-  description: Una GitHub Action para revertir o borrar un lanzamiento
-  languages: 'JavaScript'
-  href: author/action-rollback
-  tags:
-    - flujo de trabajo
-    - releases
-- 
-  title: Bloquear propuestas y solicitudes de cambios cerradas
-  description: Una GitHub Action que bloquea propuestas y solicitudes de cambios cerrads después de un periodo de inactividad
-  languages: 'JavaScript'
-  href: dessant/lock-threads
-  tags:
-    - propuestas
-    - solicitudes de extracción
-    - flujo de trabajo
-- 
-  title: Obtiene un conteo de diferencias en confirmaciones entre dos ramas
-  description: Esta GitHub Action compara dos ramas y te proporciona el conteo de confirmaciones entre ellas
-  languages: 'JavaScript, Shell'
-  href: jessicalostinspace/commit-difference-action
-  tags:
-    - confirmación
-    - diferencia
-    - flujo de trabajo
-- 
-  title: Genera notas de lanzamiento con base en las referencias de Git
-  description: GitHub Action para generar registros de cambios y notas de lanzamiento
-  languages: 'JavaScript, Shell'
-  href: metcalfc/changelog-generator
-  tags:
-    - cicd
-    - notas de lanzamiento
-    - flujo de trabajo
-    - bitácora de Cambios
-- 
-  title: Requiere políticas en las confirmaciones y repositorios de GitHub
-  description: Requerimiento de políticas para tus redes de comunicación interna
-  languages: 'Go, Makefile, Dockerfile, Shell'
-  href: talos-systems/conform
-  tags:
-    - docker
-    - build-automation
-    - flujo de trabajo
-- 
-  title: Auto Etiquetado Basado en Propuestas
-  description: Etiqueta automáticamente una propuesta con base en su descripción
-  languages: 'TypeScript, JavaScript, Dockerfile'
-  href: Renato66/auto-label
-  tags:
-    - etiquetas
-    - flujo de trabajo
-    - automatización
-- 
-  title: Actualiza las GitHub Actions configuradas a sus últimas versiones
-  description: Herramienta de CLI para verificar si todas tus acciones están actualizadas o no
-  languages: 'C#, Inno Setup, PowerShell, Shell'
-  href: fabasoad/ghacu
-  tags:
-    - versions
-    - cli
-    - flujo de trabajo
-- 
-  title: Crear Rama de Propuesta
-  description: GitHub Action que automatiza la creación de ramas de propuestas
-  languages: 'JavaScript, Shell'
-  href: robvanderleek/create-issue-branch
-  tags:
-    - probot
-    - propuestas
-    - etiquetas
-- 
-  title: Elimina artefactos antiguos
-  description: Personaliza la limpieza de artefactos
-  languages: 'JavaScript, Shell'
-  href: c-hive/gha-remove-artifacts
-  tags:
-    - artefactos
-    - flujo de trabajo
-- 
-  title: Sincroniza los archivos/binarios definidos a un Wiki o a repositorios externos
-  description: GitHub Action para sincronizar automáticamente los cambios a los repositorios externos, como el wiki, por ejemplo
-  languages: 'Shell, Dockerfile'
-  href: kai-tub/external-repo-sync-action
-  tags:
-    - wiki
-    - sync
-    - flujo de trabajo
-- 
-  title: Crea/Actualiza/Borra una página de Wiki de GitHub con base en cualquier archivo
-  description: Actualiza tu wiki de GitHub utilizando rsync, lo cual permite la exclusión de archivops y directorios y el borrado real de los archivos
-  languages: 'Shell, Dockerfile'
-  href: Andrew-Chen-Wang/github-wiki-action
-  tags:
-    - wiki
-    - docker
-    - flujo de trabajo
-- 
-  title: GitHub Actions de Prow
-  description: Automatización del requerimiento de políticas, chat-ops y fusión automática de PR
-  languages: 'TypeScript, JavaScript'
-  href: jpmcb/prow-github-actions
-  tags:
-    - chat-ops
-    - prow
-    - flujo de trabajo
-- 
-  title: Verifica el estado de GitHub en tu flujo de trabajo
-  description: Verifica el estado de GitHub en tu flujo de trabajo
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-status
-  tags:
-    - estado
-    - supervisar
-    - flujo de trabajo
-- 
-  title: Administra etiquetas en GitHub como código
-  description: GitHub Action para administrar etiquetas (create/rename/update/delete)
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-labeler
-  tags:
-    - etiquetas
-    - flujo de trabajo
-    - automatización
-- 
-  title: Distribuir los fondos en los proyectos gratuitos y de código abierto
-  description: Distribución contínua de los fondos para los contribuyentes y dependencias de los proyectos
-  languages: 'Python, Dockerfile, Shell, Ruby'
-  href: protontypes/libreselery
-  tags:
-    - sponsors
-    - financiamiento
-    - payment
-- 
-  title: Reglas de Herald para GitHub
-  description: Agregar revisores, suscriptores, etiquetas y asignados a tu PR
-  languages: 'TypeScript, JavaScript'
-  href: gagoar/use-herald-action
-  tags:
-    - reviewers
-    - etiquetas
-    - asignatarios
-    - solicitud de cambios
-- 
-  title: Validador de Codeowner
-  description: Garantiza la exactitud de tu archivo de GitHub CODEOWNERS, apoya a los repositorios públicos y privados de GitHub y también a las instalaciones de GitHub Enterprise
-  languages: 'Go, Shell, Makefile, Dockerfile'
-  href: mszostok/codeowners-validator
-  tags:
-    - codeowners
-    - validar
-    - flujo de trabajo
-- 
-  title: Acción Copybara
-  description: Mueve y transfora el código entre los repositorios (ideal para mantener varios repositorios fuera de un mono-repositorio)
-  languages: 'TypeScript, JavaScript, Shell'
-  href: olivr/copybara-action
-  tags:
-    - monorepo
-    - copybara
-    - flujo de trabajo
-- 
-  title: Despliega archivos estáticos a GitHub Pages
-  description: GitHub Action para publcar un sitio web en GitHub Pages automáticamente
-  languages: 'TypeScript, JavaScript'
-  href: peaceiris/actions-gh-pages
-  tags:
-    - publicar
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml
new file mode 100644
index 0000000000..aa75d8eaed
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml
@@ -0,0 +1,20 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
+  bugs:
+    - 'Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.'
+    - 'When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn''t match due to the timezone not being transformed to UTC.'
+    - 'The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.'
+    - 'Spurious error messages concerning the `cloud-config.service` would be output to the console.'
+    - 'When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.'
+  changes:
+    - 'The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.'
+  known_issues:
+    - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+    - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.'
+    - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml
new file mode 100644
index 0000000000..f5d9059926
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml
@@ -0,0 +1,24 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
+  bugs:
+    - 'Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.'
+    - 'When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn''t match due to the timezone not being transformed to UTC.'
+    - 'Spurious error messages concerning the `cloud-config.service` would be output to the console.'
+    - 'The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.'
+    - 'Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.'
+    - 'When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.'
+    - 'The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.'
+    - 'Several documentation links resulted in a 404 Not Found error.'
+  changes:
+    - 'The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.'
+  known_issues:
+    - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+    - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+    - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.'
+    - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml
new file mode 100644
index 0000000000..4cf4a127e7
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml
@@ -0,0 +1,25 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
+  bugs:
+    - 'Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.'
+    - 'Migrations could fail when {% data variables.product.prodname_actions %} was enabled.'
+    - 'When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn''t match due to the timezone not being transformed to UTC.'
+    - 'Spurious error messages concerning the `cloud-config.service` would be output to the console.'
+    - 'The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.'
+    - 'Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.'
+    - 'When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.'
+    - 'When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.'
+    - 'The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.'
+    - 'A long-running database migration related to Security Alert settings could delay upgrade completion.'
+  changes:
+    - 'The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.'
+  known_issues:
+    - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
+    - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+    - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml
new file mode 100644
index 0000000000..87f6d857f5
--- /dev/null
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/3.yml
@@ -0,0 +1,28 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - '**MEDIUM**:  Secret Scanning API calls could return alerts for repositories outside the scope of the request.'
+    - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
+  bugs:
+    - 'Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.'
+    - 'Migrations could fail when {% data variables.product.prodname_actions %} was enabled.'
+    - 'When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn''t match due to the timezone not being transformed to UTC.'
+    - 'Spurious error messages concerning the `cloud-config.service` would be output to the console.'
+    - 'The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.'
+    - 'Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.'
+    - 'When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.'
+    - 'The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.'
+    - 'When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.'
+    - 'A long-running database migration related to Security Alert settings could delay upgrade completion.'
+  changes:
+    - 'The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.'
+  known_issues:
+    - 'Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.'
+    - 'On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.'
+    - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.'
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
+    - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
+    - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.'
diff --git a/translations/es-ES/data/reusables/actions/oidc-permissions-token.md b/translations/es-ES/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..4c14e9e4ed
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,13 @@
+The job or workflow run requires a `permissions` setting with [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). This allows the JWT to be requested from GitHub's OIDC provider using one of these approaches:
+
+- Using environment variables on the runner (`ACTIONS_ID_TOKEN_REQUEST_URL` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Using `getIDToken()` from the Actions toolkit.
+
+If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por ejemplo:
+
+```yaml{:copy}
+permissions:
+  id-token: write
+```
+
+Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo. 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/translations/es-ES/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
index 1e652a783b..7dc9c4e12a 100644
--- a/translations/es-ES/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
+++ b/translations/es-ES/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 
 {% note %}
 
diff --git a/translations/es-ES/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/es-ES/data/reusables/code-scanning/beta-codeql-ml-queries.md
new file mode 100644
index 0000000000..133b760b30
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -0,0 +1,9 @@
+{% if codeql-ml-queries %}
+
+{% note %}
+
+**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites-explanation.md
new file mode 100644
index 0000000000..23842c5a4a
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -0,0 +1,5 @@
+Las siguientes suites de consultas se compilan en el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} y están disponibles para utilizarse.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% if codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md
index f96857d61b..c4b52f200f 100644
--- a/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md
+++ b/translations/es-ES/data/reusables/code-scanning/codeql-query-suites.md
@@ -1,8 +1,4 @@
-Las siguientes suites de consultas se compilan en el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} y están disponibles para utilizarse.
-
   | Conjunto de consultas  | Descripción                                                                          |
   |:---------------------- |:------------------------------------------------------------------------------------ |
   | `security-extended`    | Las consultas de severidad y precisión más baja que aquellas predeterminadas         |
   | `security-and-quality` | Las consultas de `security-extended`, mas aquellas de mantenibilidad y confiabilidad |
-
-Cuando especificas una suite de consultas, el motor de análisis de {% data variables.product.prodname_codeql %} ejecutará las consultas dentro de la suite para ti, adicionalmente a el conjunto de consultas adicional.
diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-billing.md b/translations/es-ES/data/reusables/codespaces/codespaces-billing.md
index 60393bb900..818220cec3 100644
--- a/translations/es-ES/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/es-ES/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
 Los {% data variables.product.prodname_codespaces %} se cobran en dólares estadounidenses (USD) de acuerdo con su uso de almacenamiento y cálculo.
 
 ### Calcular el uso de cómputo
-La cantidad total de tiempo de actividad en minutos durante la cual están activas las instancias de {% data variables.product.prodname_codespaces %}. El uso de cómputo se calcula mediante la cantidad real de minutos que utilizan todos los codespaces. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente.
+Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente.
 
-El tiempo de actividad se controla deteniendo tu codespace, lo cual puede hacerse manualmente o con base en un periodo de inactividad. Para obtener más información, consulta la sección "[Cerrar o detener tu codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. Para obtener más información, consulta la sección "[Cerrar o detener tu codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
 
 ### Calcular el uso de almacenamiento
 Para propósitos de facturación de {% data variables.product.prodname_codespaces %}, esto incluye todo el almacenamiento que utilizan todos los codespaces en tu cuenta. Esto incluye cualquier archivo que utilicen los codespaces, tales como los repositorios clonados, archivos de configuración y extensiones, entre otros. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. 
diff --git a/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md b/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md
index 20de5c6bf9..d0dd03f585 100644
--- a/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md
+++ b/translations/es-ES/data/reusables/enterprise_management_console/save-settings.md
@@ -1,2 +1,2 @@
 1. Debajo de la barra lateral izquierda, da clic en **Guardar configuración**. ![El botón de guardar en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-1. Espera a que la configuración se ejecute por completo.
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..a1cc2ae3c0
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.product.product_location %}.
+
+{% endwarning %}
diff --git a/translations/es-ES/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/translations/es-ES/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..b064065a09
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,3 @@
+1. Espera a que la configuración se ejecute por completo.
+
+   ![Configurar tu instancia](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md b/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md
index 0811bb65bf..319b8698fd 100644
--- a/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md
+++ b/translations/es-ES/data/reusables/gated-features/user-repo-collaborators.md
@@ -1 +1,4 @@
-Si estás utilizando {% data variables.product.prodname_free_user %}, puedes agregar colaboradores ilimitados en repositorios públicos y privados.
+{% ifversion fpt %}
+If you're using
+{% data variables.product.prodname_free_user %}, you can add unlimited collaborators on public and private repositories.
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/billing-settings.md b/translations/es-ES/data/reusables/organizations/billing-settings.md
index 45d230b82a..feb35fd556 100644
--- a/translations/es-ES/data/reusables/organizations/billing-settings.md
+++ b/translations/es-ES/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
 {% data reusables.user_settings.access_settings %}
-2. In the settings sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% data reusables.profile.org_settings %}
-1. If you're an organization owner, in the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/es-ES/data/reusables/organizations/oauth_app_access.md b/translations/es-ES/data/reusables/organizations/oauth_app_access.md
index f8220ca98f..a2dc8773f5 100644
--- a/translations/es-ES/data/reusables/organizations/oauth_app_access.md
+++ b/translations/es-ES/data/reusables/organizations/oauth_app_access.md
@@ -1,3 +1 @@
-{% ifversion fpt or ghec %}
-  1. En la barra lateral de configuración, da clic en **Acceso de terceros**. ![pestaña de acceso de {% data variables.product.prodname_oauth_app %} en la barra lateral izquierda](/assets/images/help/settings/settings-sidebar-third-party-access.png)
-{% endif %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
diff --git a/translations/es-ES/data/reusables/organizations/teams_sidebar.md b/translations/es-ES/data/reusables/organizations/teams_sidebar.md
index ff6322eefe..082f84c9a5 100644
--- a/translations/es-ES/data/reusables/organizations/teams_sidebar.md
+++ b/translations/es-ES/data/reusables/organizations/teams_sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
 1. En la barra lateral de Configuración, da clic en **Equipos**. ![Pestaña de equipos en la barra lateral de configuración de la organización](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/profile/org_member_privileges.md b/translations/es-ES/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..c0462ae849
--- /dev/null
+++ b/translations/es-ES/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1 @@
+3. Under "Access", click **Member privileges**. ![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png) 
diff --git a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
index 8634453272..eb6745e85c 100644
--- a/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/es-ES/data/reusables/repositories/sidebar-notifications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
 1. Da clic en **Notificaciones**. ![Botón de notificaciones en la barra lateral](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/security/compliance-report-list.md b/translations/es-ES/data/reusables/security/compliance-report-list.md
new file mode 100644
index 0000000000..a8d6d1a87e
--- /dev/null
+++ b/translations/es-ES/data/reusables/security/compliance-report-list.md
@@ -0,0 +1,4 @@
+- SOC 1, Tipo 2
+- SOC 2, Tipo 2
+- Cloud Security Alliance CAIQ self-assessment (CSA CAIQ)
+- {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/security/compliance-report-screenshot.md b/translations/es-ES/data/reusables/security/compliance-report-screenshot.md
new file mode 100644
index 0000000000..984c8d6d8b
--- /dev/null
+++ b/translations/es-ES/data/reusables/security/compliance-report-screenshot.md
@@ -0,0 +1 @@
+![Screenshot of download button to the right of a compliance report](/assets/images/help/settings/compliance-report-download.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/sponsors/sponsors-only-repos.md b/translations/es-ES/data/reusables/sponsors/sponsors-only-repos.md
new file mode 100644
index 0000000000..0361572c97
--- /dev/null
+++ b/translations/es-ES/data/reusables/sponsors/sponsors-only-repos.md
@@ -0,0 +1 @@
+You can give all sponsors in a tier access to a private repository by adding the repository to the tier.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/sponsors/tier-details.md b/translations/es-ES/data/reusables/sponsors/tier-details.md
index 1b4d56cf8e..2c67994552 100644
--- a/translations/es-ES/data/reusables/sponsors/tier-details.md
+++ b/translations/es-ES/data/reusables/sponsors/tier-details.md
@@ -3,10 +3,11 @@ Puedes crear hasta 10 niveles de patrocinio de una sola ocasión y 10 niveles me
 Puedes personalizar las recompensas de cada nivel. Por ejemplo, las recompensas de un nivel podrían incluir:
 - Acceso temprano a versiones nuevas
 - Logo o nombre en el README
-- Acceder a un repositorio privado
 - Actualizaciones del boletín semanal
 - Otras recompensas de las cuales disfrutarían tus patrocinadores ✨
 
+{% data reusables.sponsors.sponsors-only-repos %} For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)."
+
 Puedes incluir un mensaje de bienvenida con información sobre cómo acceder o recibir recompensas, el cual se podrá ver después de hacer el pago y en el correo electrónico de bienvenida.
 
 Una vez que hayas publicado un nivel, no podrás editar el precio del mismo. En vez de eso, deberás retirar el nivel y crear uno nuevo. Los patrocinadores existentes seguirán en el nivel que se retiró hasta que cambian su nivel de patrocinio, cancelen su patrocinio, o venza su periodo de patrocinio de una sola ocasión.
diff --git a/translations/es-ES/data/reusables/user-settings/oauth_apps.md b/translations/es-ES/data/reusables/user-settings/oauth_apps.md
index 95382c6168..83327580ce 100644
--- a/translations/es-ES/data/reusables/user-settings/oauth_apps.md
+++ b/translations/es-ES/data/reusables/user-settings/oauth_apps.md
@@ -1 +1 @@
-1. En la barra lateral izquierda, haz clic en **Apps de OAuth**. ![Sección de la App de OAuth](/assets/images/help/settings/developer-settings-oauth-apps.png)
+1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_oauth_apps %}**. ![Sección de la App de OAuth](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/es-ES/data/reusables/user_settings/access_applications.md b/translations/es-ES/data/reusables/user_settings/access_applications.md
index 090911a90e..2fe392350c 100644
--- a/translations/es-ES/data/reusables/user_settings/access_applications.md
+++ b/translations/es-ES/data/reusables/user_settings/access_applications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
 1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de aplicaciones](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/accessibility_settings.md b/translations/es-ES/data/reusables/user_settings/accessibility_settings.md
index b23486a3ff..2c9e37e2f4 100644
--- a/translations/es-ES/data/reusables/user_settings/accessibility_settings.md
+++ b/translations/es-ES/data/reusables/user_settings/accessibility_settings.md
@@ -1 +1 @@
-1. In the navigation on the left hand side, click the **Accessibility** link. ![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)
+1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**.
diff --git a/translations/es-ES/data/reusables/user_settings/account_settings.md b/translations/es-ES/data/reusables/user_settings/account_settings.md
index c38c7bbe42..6adb2aee80 100644
--- a/translations/es-ES/data/reusables/user_settings/account_settings.md
+++ b/translations/es-ES/data/reusables/user_settings/account_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+1. En la barra lateral izquierda, haz clic en **{% octicon "gear" aria-label="The gear icon" %} Account** (Cuenta).
+{% else %}
 1. En la barra lateral izquierda, da clic en **Cuenta**. ![Opción de menú de configuración de cuenta](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/appearance-settings.md b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
index c9e1b3641a..5b3fb50d32 100644
--- a/translations/es-ES/data/reusables/user_settings/appearance-settings.md
+++ b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Apariencia**.
 
-   ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
+   ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/user_settings/billing_plans.md b/translations/es-ES/data/reusables/user_settings/billing_plans.md
index 471f9e8da1..333102205b 100644
--- a/translations/es-ES/data/reusables/user_settings/billing_plans.md
+++ b/translations/es-ES/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. En la barra lateral de configuración de usuario, haz clic en **Facturación & planes**. ![Configuración de facturación & planes](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/es-ES/data/reusables/user_settings/blocked_users.md b/translations/es-ES/data/reusables/user_settings/blocked_users.md
index 1e9de2840a..b7ba502dca 100644
--- a/translations/es-ES/data/reusables/user_settings/blocked_users.md
+++ b/translations/es-ES/data/reusables/user_settings/blocked_users.md
@@ -1 +1 @@
-1. En tu barra lateral de ajustes de usuario, haz clic en **Usuarios bloqueados** debajo de **Ajustes de moderación**. ![Pestaña de usuarios bloqueados](/assets/images/help/settings/settings-sidebar-blocked-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**.
diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md
index af92d527b7..5aa532885e 100644
--- a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md
+++ b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md
@@ -1 +1 @@
-1. En la barra lateral izquierda, da clic en **Codespaces**. ![Pestaña de Codespaces en la barra lateral de la configuración de usuario](/assets/images/help/settings/codespaces-tab.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/es-ES/data/reusables/user_settings/developer_settings.md b/translations/es-ES/data/reusables/user_settings/developer_settings.md
index e1268dd5a0..2313297a74 100644
--- a/translations/es-ES/data/reusables/user_settings/developer_settings.md
+++ b/translations/es-ES/data/reusables/user_settings/developer_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %}
 1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Configuración de desarrollador](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/emails.md b/translations/es-ES/data/reusables/user_settings/emails.md
index 793d3d5e6e..4701b9b984 100644
--- a/translations/es-ES/data/reusables/user_settings/emails.md
+++ b/translations/es-ES/data/reusables/user_settings/emails.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
 1. En la barra lateral izquierda, da clic en **Correos Electrónicos**. ![Pestaña de correos electrónicos](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/organizations.md b/translations/es-ES/data/reusables/user_settings/organizations.md
index 78aed7402b..0a19839a55 100644
--- a/translations/es-ES/data/reusables/user_settings/organizations.md
+++ b/translations/es-ES/data/reusables/user_settings/organizations.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Organizaciones**. ![Configuración de usuario para organizaciones](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/repo-tab.md b/translations/es-ES/data/reusables/user_settings/repo-tab.md
index bbf235fd23..07a8e9af62 100644
--- a/translations/es-ES/data/reusables/user_settings/repo-tab.md
+++ b/translations/es-ES/data/reusables/user_settings/repo-tab.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 1. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/saved_replies.md b/translations/es-ES/data/reusables/user_settings/saved_replies.md
index e021c903da..b47b23628e 100644
--- a/translations/es-ES/data/reusables/user_settings/saved_replies.md
+++ b/translations/es-ES/data/reusables/user_settings/saved_replies.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
 1. En la barra lateral izquierda, da clic en **Respuestas guardadas**. ![Pestaña de respuestas guardadas](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/security-analysis.md b/translations/es-ES/data/reusables/user_settings/security-analysis.md
index 833c5cd4ed..c54b43346e 100644
--- a/translations/es-ES/data/reusables/user_settings/security-analysis.md
+++ b/translations/es-ES/data/reusables/user_settings/security-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Configuración de análisis y seguridad](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/security.md b/translations/es-ES/data/reusables/user_settings/security.md
index 57c9965d30..ef37e871ec 100644
--- a/translations/es-ES/data/reusables/user_settings/security.md
+++ b/translations/es-ES/data/reusables/user_settings/security.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
 1. En la barra lateral izquierda, da clic en **Seguridad de cuenta**. ![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/ssh.md b/translations/es-ES/data/reusables/user_settings/ssh.md
index f646ee2d0d..44d51f35ff 100644
--- a/translations/es-ES/data/reusables/user_settings/ssh.md
+++ b/translations/es-ES/data/reusables/user_settings/ssh.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
 1. En la barra lateral de configuración de usuario, da clic en **Llaves SSH y GPG**. ![Llaves de autenticación](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index b5fb656a49..452428c36d 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -43,7 +43,7 @@ pages:
   article_version: 'Versión del artículo'
   miniToc: En este artículo
   contributor_callout: En este artículo contribuye y lo mantiene
-  all_enterprise_releases: Todos los lanzamientos de Enterprise
+  all_enterprise_releases: All Enterprise Server releases
 errors:
   oops: '¡Ups!'
   something_went_wrong: Parece que algo salió mal.
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
index 9a90ddeec7..dd471bd9a4 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
@@ -46,7 +46,7 @@ shortTitle: Triage your notifications
 
 たとえば、次の順序でフォローアップすることを決定できます。
   - 割り当てられた Issue およびプルリクエスト。 可能な Issue またはプルリクエストをすぐにクローズして、更新を追加します。 必要に応じて、後で確認するために通知を保存します。
-  - 保存済インボックスの通知、特に未読の更新を確認します。 スレッドが不要になった場合は、{% octicon "bookmark" aria-label="The bookmark icon" %} をオフにして、通知を保存済インボックスから削除し、保存を解除します。
+  - 保存済インボックスの通知、特に未読の更新を確認します。 If the thread is no longer relevant, deselect {% octicon "bookmark" aria-label="The bookmark icon" %} to remove the notification from the saved inbox and unsave it.
 
 ## 優先度の低い通知を管理する
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
index 9084cb9a07..7afb8f3d39 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -28,7 +28,7 @@ For more information about how contributions are calculated, see "[Managing cont
 {% note %}
 
 **Notes:**
-- The connection between your accounts is governed by <a href="/articles/github-privacy-statement/" class="dotcom-only">GitHub's Privacy Statement</a> and users enabling the connection agree to the <a href="/articles/github-terms-of-service/" class="dotcom-only">GitHub's Terms of Service</a>.
+- The connection between your accounts is governed by [GitHub's Privacy Statement](/free-pro-team@latest/github/site-policy/github-privacy-statement/) and users enabling the connection agree to the [GitHub's Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service).
 
 - Before you can connect your {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner.
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 2a3bba883f..ca10250041 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
-product: '{% ifversion fpt %}{% data reusables.gated-features.user-repo-collaborators %}{% endif %}'
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -38,8 +38,8 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
 1. コラボレーターとして招待する人のユーザ名を確認してください。{% ifversion fpt or ghec %}まだユーザ名がない場合は、{% data variables.product.prodname_dotcom %}にサインアップできます。詳細は「[新しい {% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/articles/signing-up-for-a-new-github-account)」を参照してください。{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
+{% data reusables.repositories.click-collaborators-teams %}
 1. [**Invite a collaborator**] をクリックします。 ![[Invite a collaborator] ボタン](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. 検索フィールドで、招待する人の名前を入力し、一致するリストの名前をクリックします。 ![リポジトリに招待する人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field-user.png)
 3. [**Add NAME to REPOSITORY**] をクリックします。 ![コラボレーターを追加するボタン](/assets/images/help/repository/add-collaborator-user-repo.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 0a9b07c89a..540062333f 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -30,8 +30,8 @@ shortTitle: Remove a collaborator
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. 削除するコラボレーターの右で、{% octicon "trash" aria-label="The trash icon" %} をクリックします。 ![コラボレーターを削除するボタン](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. 左のサイドバーで、[**Collaborators & teams**] をクリックします。 ![[Collaborators] タブ](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index ab925962e6..912484a983 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -9,7 +9,6 @@ redirect_from:
   - /articles/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
-product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -22,6 +21,10 @@ shortTitle: Remove yourself
 ---
 
 {% data reusables.user_settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 2. 左のサイドバーで [**Repositories**] をクリックします。 ![[Repositories] タブ](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
 3. 離脱するリポジトリの横にある [**Leave**] をクリックします。 ![[Leave] ボタン](/assets/images/help/repository/repo-leave.png)
 4. 警告をよく読んでから [I understand, leave this repository.] をクリックします。 ![本当に離脱してよいか確認を促すダイアログボックス](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
index ee5e8720f4..cdd67a3025 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -13,12 +13,12 @@ shortTitle: Integrate Jira with projects
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
-3. 左のサイドバーで**{% data variables.product.prodname_oauth_apps %}**をクリックしてください。 ![左のサイドバーの{% data variables.product.prodname_oauth_apps %}タブ](/assets/images/help/settings/developer-settings-oauth-apps.png)
-3. [**Register a new application**] をクリックします。
-4. [**Application name**] に "Jira" と入力します。
-5. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。
-6. [**Authorization callback URL**] に、JIRA インスタンスの完全な URL を入力します。
-7. **Register application** をクリックする。 ![[Register application] ボタン](/assets/images/help/oauth/register-application-button.png)
+{% data reusables.user-settings.oauth_apps %}
+1. [**Register a new application**] をクリックします。
+2. [**Application name**] に "Jira" と入力します。
+3. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。
+4. [**Authorization callback URL**] に、JIRA インスタンスの完全な URL を入力します。
+5. **Register application** をクリックする。 ![[Register application] ボタン](/assets/images/help/oauth/register-application-button.png)
 8. [**Developer applications**] で、[Client ID] と [Client Secret] の値を確認します。 ![クライアント ID とクライアントシークレット](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 027eeacccb..e448e15fc4 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,5 +14,5 @@ shortTitle: Managing your tab size
 If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings.
 
 {% data reusables.user_settings.access_settings %}
-1. [User settings] サイドバーで、[**Appearance**] をクリックします。 ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png)
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 2. Under "Tab size preference", select the drop-down menu and choose your preference. ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
index cb6ed4d2fb..025124c55f 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
@@ -26,8 +26,7 @@ shortTitle: スケジュールされたリマインダーの管理
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. リマインダーをスケジュールしたい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. リマインダーをスケジュールしたい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.days-dropdown %}
@@ -41,16 +40,14 @@ shortTitle: スケジュールされたリマインダーの管理
 ## ユーザアカウントのスケジュールされたリマインダーを管理する
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. スケジュールされたリマインダーを編集したい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. スケジュールされたリマインダーを編集したい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
 
 ## ユーザアカウントのスケジュールされたリマインダーを削除する
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. リマインダーを削除したい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. リマインダーを削除したい Organization の隣で [**Edit**] をクリックします。 ![[Scheduled reminders edit] ボタン](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.delete %}
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index f0aee747c1..14b31d5a37 100644
--- a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -88,7 +88,7 @@ Multiple workflows within a repository share cache entries. A cache created for
 ### `cache` アクションの入力パラメータ
 
 - `key`: **必須** このキーはキャッシュの保存時に作成され、キャッシュの検索に使われます。 変数、コンテキスト値、静的な文字列、関数の任意の組み合わせが使えます。 キーの長さは最大で512文字であり、キーが最大長よりも長いとアクションは失敗します。
-- `path`: **必須** ランナーがキャッシュあるいはリストアをするファイルパス。 このパスは、絶対パスでも、ワーキングディレクトリからの相対パスでもかまいません。
+- `path`: **必須** ランナーがキャッシュあるいはリストアをするファイルパス。 The path can be an absolute path or relative to the workspace directory.
   - パスはディレクトリまたは単一ファイルのいずれかで、glob パターンがサポートされています。
   - `cache` アクションの `v2` では、単一のパスを指定することも、別々の行に複数のパスを追加することもできます。 例:
     ```
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 826b4676f1..79b9262838 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -238,7 +238,7 @@ jobs:
 
 ## コードの文法チェック
 
-以下の例は`rubocop`をインストールし、それを使ってすべてのファイルの文法チェックを行います。 詳しい情報については[ Rubocop](https://github.com/rubocop-hq/rubocop)を参照してください。 特定の文法チェックルールを決めるために、[ Rubocopを設定](https://docs.rubocop.org/rubocop/configuration.html)できます。
+以下の例は`rubocop`をインストールし、それを使ってすべてのファイルの文法チェックを行います。 For more information, see [RuboCop](https://github.com/rubocop-hq/rubocop). 特定の文法チェックルールを決めるために、[ Rubocopを設定](https://docs.rubocop.org/rubocop/configuration.html)できます。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
index 478112e49e..82aba25cc7 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
@@ -84,7 +84,9 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
         - id: random-number-generator
           run: echo "::set-output name=random-id::$(echo $RANDOM)"
           shell: bash
-        - run: ${{ github.action_path }}/goodbye.sh
+        - run: echo "${{ github.action_path }}" >> $GITHUB_PATH
+          shell: bash          
+        - run: goodbye.sh
           shell: bash
     ```
     {% endraw %}
diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index c1fb306a90..ddaf64d2b5 100644
--- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -47,6 +47,8 @@ DockerアクションはデフォルトのDockerユーザ（root）で実行さ
 
 Dockerの`ENTRYPOINT`命令には、_shell_形式と_exec_形式があります。 Dockerの`ENTRYPOINT`のドキュメンテーションは、`ENTRYPOINT`の_exec_形式を使うことを勧めています。 _exec_および_shell_形式に関する詳しい情報については、Dockerのドキュメンテーション中の[ENTRYPOINTのリファレンス](https://docs.docker.com/engine/reference/builder/#entrypoint)を参照してください。
 
+You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
+
 _exec_形式の`ENTRYPOINT`命令を使うようにコンテナを設定した場合、アクションのメタデータファイル中に設定された`args`はコマンドシェル内では実行されません。 アクションの`args`に環境変数が含まれている場合、その変数は置換されません。 たとえば、以下の_exec_形式は`$GITHUB_SHA`に保存された値を出力せず、代わりに`"$GITHUB_SHA"`を出力します。
 
 ```dockerfile
diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index c7f923dd53..12ace91be1 100644
--- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -13,6 +13,7 @@ versions:
   ghae: '*'
   ghec: '*'
 type: reference
+miniTocMaxHeadingLevel: 4
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -20,7 +21,7 @@ type: reference
 
 ## {% data variables.product.prodname_actions %}のYAML構文について
 
-Docker及びJavaScriptアクションにはメタデータファイルが必要です。 このメタデータのファイル名は`action.yml`もしくは`action.yaml`でなければなりません。 メタデータファイル中のデータは、アクションの入力、出力、メインエントリポイントを定義します。
+All actions require a metadata file. このメタデータのファイル名は`action.yml`もしくは`action.yaml`でなければなりません。 The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
 
 アクションのメタデータファイルはYAML構文を使います。 YAMLについて詳しくない場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。
 
@@ -40,7 +41,7 @@ Docker及びJavaScriptアクションにはメタデータファイルが必要
 
 **オプション** inputsパラメーターを使うと、アクションが実行時に使うデータを指定できます。 {% data variables.product.prodname_dotcom %}は、inputsパラメータを環境変数として保存します。 大文字が使われているInputsのidは、実行時に小文字に変換されます。 inputsのidには小文字を使うことをおすすめします。
 
-### サンプル
+### Example: Specifying inputs
 
 この例では、numOctocatsとoctocatEyeColorという 2つの入力を設定しています。 入力のnumOctocatsは必須ではなく、デフォルトの値は'1'になっています。 入力のoctocatEyeColorは必須であり、デフォルト値を持ちません。 このアクションを使うワークフローのファイルは、`with`キーワードを使ってoctocatEyeColorの入力値を設定しなければなりません。 `with`構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)」を参照してください。
 
@@ -83,13 +84,13 @@ To access the environment variable in a Docker container action, you must pass t
 
 **オプション** 入力パラメータが使用されている場合、この `string` は警告メッセージとしてログに記録されます。 この警告で入力が非推奨であることをユーザに通知し、その他の方法を知らせることができます。
 
-## `outputs`
+## `outputs` for Docker container and JavaScript actions
 
 **オプション** アクションが設定するデータを宣言できる出力パラメータ。 ワークフローで後に実行されるアクションは、先行して実行されたアクションが設定した出力データを利用できます。  たとえば、2つの入力を加算(x + y = z)するアクションがあれば、そのアクションは他のアクションが入力として利用できる合計値(z)を出力できます。
 
 メタデータファイル中でアクション内の出力を宣言しなくても、出力を設定してワークフロー中で利用することはできます。 アクション中での出力の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)」を参照してください。
 
-### サンプル
+### Example: Declaring outputs for Docker container and JavaScript actions
 
 ```yaml
 outputs:
@@ -107,9 +108,9 @@ outputs:
 
 ## `outputs` for composite actions
 
-**オプション** `outputs` `outputs.<output_id>` および `outputs.<output_id>.description`（「[{% data variables.product.prodname_actions %} の `outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)」を参照）と同じパラメーターを使用しますが、`value` トークンも含まれます。
+**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
 
-### サンプル
+### Example: Declaring outputs for composite actions
 
 {% raw %}
 ```yaml
@@ -134,13 +135,13 @@ For more information on how to use context syntax, see "[Contexts](/actions/lear
 
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
+**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
 
 ## JavaScriptアクションのための`runs`
 
 **Required** Configures the path to the action's code and the runtime used to execute the code.
 
-### Example using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
+### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
@@ -159,9 +160,9 @@ runs:
 
 **必須** アクションのコードを含むファイル。 The runtime specified in [`using`](#runsusing) executes this file.
 
-### `pre`
+### `runs.pre`
 
-**オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. `pre:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。
+**オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
 
 この例では、`pre:`アクションは`setup.js`というスクリプトを実行します。
 
@@ -173,7 +174,7 @@ runs:
   post: 'cleanup.js'
 ```
 
-### `pre-if`
+### `runs.pre-if`
 
 **オプション** `pre:`アクションの実行条件を定義できるようにしてくれます。 `pre:`アクションは、`pre-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`pre-if`のデフォルトは`always()`になります。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
 
@@ -186,7 +187,7 @@ runs:
   pre-if: runner.os == 'linux'
 ```
 
-### `post`
+### `runs.post`
 
 **オプション** `main:`アクションの終了後、ジョブの終わりにスクリプトを実行できるようにします。 たとえば、`post:`を使って特定のプロセスを終了させたり、不要なファイルを削除したりできます。 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
@@ -201,7 +202,7 @@ runs:
 
 `post:`アクションはデフォルトで常に実行されますが、`post-if`を使ってこれをオーバーライドすることができます。
 
-### `post-if`
+### `runs.post-if`
 
 **オプション** `post:`アクションの実行条件を定義できるようにしてくれます。 `post:`アクションは、`post-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`post-if`のデフォルトは`always()`になります。 In `post-if`, status check functions evaluate against the job's status, not the action's own status.
 
@@ -266,6 +267,7 @@ runs:
 **必須** コマンドを実行するシェル。 [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set.
 {% endif %}
 
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 #### `runs.steps[*].if`
 
 **Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
@@ -294,6 +296,7 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
     uses: actions/heroku@1.0.0
 ```
+{% endif %}
 
 #### `runs.steps[*].name`
 
@@ -362,11 +365,11 @@ runs:
 ```
 {% endif %}
 
-## Dockerアクションのための`runs`
+## `runs` for Docker container actions
 
-**必須** Dockerアクションのために使われるイメージを設定します。
+**Required** Configures the image used for the Docker container action.
 
-### リポジトリでのDockerfileの利用例
+### Example: Using a Dockerfile in your repository
 
 ```yaml
 runs:
@@ -374,7 +377,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-### パブリックなDockerレジストリコンテナを利用する例
+### Example: Using public Docker registry container
 
 ```yaml
 runs:
@@ -386,9 +389,9 @@ runs:
 
 **必須** この値は`'docker'`に設定しなければなりません。
 
-### `pre-entrypoint`
+### `runs.pre-entrypoint`
 
-**オプション** `entrypoint`アクションが始まる前にスクリプトを実行できるようにしてくれます。 たとえば、`pre-entrypoint:`を使って必要なセットアップスクリプトを実行できます。 {% data variables.product.prodname_actions %}は`docker run`を使ってこのアクションを起動し、同じベースイメージを使う新しいコンテナ内でスクリプトを実行します。 これはすなわち、ランタイムの状態はメインの`entrypoint`コンテナとは異なるということで、必要な状態はワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスしなければなりません。 `pre-entrypoint:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。
+**オプション** `entrypoint`アクションが始まる前にスクリプトを実行できるようにしてくれます。 たとえば、`pre-entrypoint:`を使って必要なセットアップスクリプトを実行できます。 {% data variables.product.prodname_actions %}は`docker run`を使ってこのアクションを起動し、同じベースイメージを使う新しいコンテナ内でスクリプトを実行します。 これはすなわち、ランタイムの状態はメインの`entrypoint`コンテナとは異なるということで、必要な状態はワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスしなければなりません。 The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
 
 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
@@ -420,7 +423,7 @@ runs:
 
 ### `post-entrypoint`
 
-**オプション** `run.entrypoint`アクションが完了した後に、クリーンアップスクリプトを実行できるようにしてくれます。 {% data variables.product.prodname_actions %}はこのアクションを起動するのに`docker run`を使います。 {% data variables.product.prodname_actions %}はスクリプトを同じベースイメージを使って新しいコンテナ内で実行するので、ランタイムの状態はメインの`entrypoint`コンテナとは異なります。 必要な状態には、ワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスできます。 `post-entrypoint:`アクションはデフォルトで常に実行されますが、[`post-if`](#post-if)を使ってこれをオーバーライドすることができます。
+**オプション** `run.entrypoint`アクションが完了した後に、クリーンアップスクリプトを実行できるようにしてくれます。 {% data variables.product.prodname_actions %}はこのアクションを起動するのに`docker run`を使います。 {% data variables.product.prodname_actions %}はスクリプトを同じベースイメージを使って新しいコンテナ内で実行するので、ランタイムの状態はメインの`entrypoint`コンテナとは異なります。 必要な状態には、ワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスできます。 The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
 
 ```yaml
 runs:
@@ -444,7 +447,7 @@ runs:
 
 {% data variables.product.prodname_actions %}での`CMD`命令の利用に関する詳しい情報については、「[{% data variables.product.prodname_actions %}のDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)」を参照してください。
 
-#### サンプル
+#### Example: Defining arguments for the Docker container
 
 {% raw %}
 ```yaml
@@ -462,7 +465,7 @@ runs:
 
 アクションをパーソナライズして見分けられるようにするために、カラーと[Feather](https://feathericons.com/)アイコンを使ってバッジを作ることができます。 バッジは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)内のアクション名の隣に表示されます。
 
-### サンプル
+### Example: Configuring branding for an action
 
 ```yaml
 branding:
@@ -476,7 +479,12 @@ branding:
 
 ### `branding.icon`
 
-利用する[Feather](https://feathericons.com/)アイコンの名前。
+利用する[Feather](https://feathericons.com/)アイコンの名前。 <!-- 
+  This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
+  This table does not match the latest version the feather library. 
+  (Brand icons are omitted, and our supported list is not necessarily up-to-date with the latest version of the feather icon library.)
+  To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo. 
+-->
 
 <table>
 <tr>
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index a54041428e..9251cd6468 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -29,7 +29,7 @@ By updating your workflows to use OIDC tokens, you can adopt the following good
 
 - **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC.
 - **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources.
-- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single workflow run, and then automatically expires.
+- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.
 
 ### Getting started with OIDC
 
@@ -38,7 +38,7 @@ The following diagram gives an overview of how {% data variables.product.prodnam
 ![OIDC diagram](/assets/images/help/images/oidc-architecture.png)
 
 1. In your cloud provider, create an OIDC trust between your cloud role and your {% data variables.product.prodname_dotcom %} workflow(s) that need access to the cloud.
-2. Every time your {% data variables.product.prodname_actions %} workflow job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
+2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
 3. You could include a step or action in your job to request this token from {% data variables.product.prodname_dotcom %}'s OIDC provider, and present it to the cloud provider.
 4. Once the cloud provider successfully validates the claims presented in the token, it then provides a short-lived cloud access token that is available only for the duration of the job.
 
@@ -51,7 +51,7 @@ When you configure your cloud to trust {% data variables.product.prodname_dotcom
 
 ### Understanding the OIDC token
 
-Each workflow run requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. During a workflow run, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
+Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
 
 The following example OIDC token uses a subject (`sub`) that references a job environment named `prod` in the `octo-org/octo-repo` repository.
 
@@ -147,7 +147,7 @@ In addition, your cloud provider could allow you to assign a role to the access
 
 ### サンプル
 
-The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the workflow run's [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
+The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
 
 #### Filtering for a specific environment
 
@@ -217,6 +217,10 @@ You could also use a `curl` command to request the JWT, using the following envi
 curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
 ```
 
+### Adding permissions settings
+
+{% data reusables.actions.oidc-permissions-token %}
+
 ## Updating your workflows for OIDC
 
 You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index a173dae97b..4bee7a04b0 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -56,14 +56,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
@@ -93,7 +86,7 @@ jobs:
       - name: Git clone the repository
         uses: actions/checkout@v2
       - name: configure aws credentials
-        uses: aws-actions/configure-aws-credentials@master
+        uses: aws-actions/configure-aws-credentials@v1
         with:
           role-to-assume: arn:aws:iam::1234567890:role/example-role
           role-session-name: samplerolesession
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 61bb92661e..2d415572a4 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -50,14 +50,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index e7bb5db9dd..8d8b5387d5 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -37,14 +37,7 @@ If your cloud provider doesn't yet offer an official action, you can update your
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Using official actions
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index 531af3b6b3..84a65bc170 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -49,14 +49,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 04d654b13f..75aae09acc 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -54,14 +54,7 @@ This example demonstrates how to use OIDC with the official action to request a
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index 8585b4c622..d2d43e5039 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -44,7 +44,7 @@ For more information about installing and using self-hosted runners, see "[Addin
 - Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes.
 
 **Self-hosted runners:**{% endif %}
-- Receive automatic updates for the self-hosted runner application only. You are responsible for updating the operating system and all other software. 
+- Receive automatic updates for the self-hosted runner application only{% ifversion fpt or ghec or ghes > 3.2 %}, though you may disable automatic updates of the runner. For more information about controlling runner software updates on self-hosted runners, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners#controlling-runner-software-updates-on-self-hosted-runners)."{% else %}.{% endif %} You are responsible for updating the operating system and all other software.
 - Can use cloud services or local machines that you already pay for.
 - Are customizable to your hardware, operating system, software, and security requirements.
 - Don't need to have a clean instance for every job execution.
@@ -55,7 +55,7 @@ For more information about installing and using self-hosted runners, see "[Addin
 You can use any machine as a self-hosted runner as long at it meets these requirements:
 
 * You can install and run the self-hosted runner application on the machine. For more information, see "[Supported architectures and operating systems for self-hosted runners](#supported-architectures-and-operating-systems-for-self-hosted-runners)."
-* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
+* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.product_name %}](#communication-requirements)."
 * The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
 * If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
 
@@ -125,6 +125,8 @@ Some extra configuration might be required to use actions from {% data variables
 
 {% endif %}
 
+<a name="communication-requirements"></a>
+
 ## Communication between self-hosted runners and {% data variables.product.product_name %}
 
 The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs.
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 3a1090c662..bebcefdafe 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -27,12 +27,12 @@ The following repositories have detailed instructions for setting up these autos
 
 Each solution has certain specifics that may be important to consider:
 
-| **機能**                         | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
-|:------------------------------ |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
-| ランタイム                          | Kubernetes                                                                         | Linux and Windows VMs                                                 |
-| Supported Clouds               | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
-| Where runners can be scaled    | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
-| Pull-based autoscaling support | あり                                                                                 | なし                                                                    |
+| **機能**                      | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
+|:--------------------------- |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
+| ランタイム                       | Kubernetes                                                                         | Linux and Windows VMs                                                 |
+| Supported Clouds            | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
+| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
+| How runners can be scaled   | Webhook events, Scheduled, Pull-based                                              | Webhook events, Scheduled (org-level runners only)                    |
 
 ## Using ephemeral runners for autoscaling
 
@@ -42,8 +42,8 @@ This approach allows you to manage your runners as ephemeral systems, since you
 
 To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. 例:
 
-```
-$ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
+```shell
+./config.sh --url https://github.com/octo-org --token example-token --ephemeral
 ```
 
 The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered.
@@ -54,6 +54,28 @@ The {% data variables.product.prodname_actions %} service will then automaticall
 
 {% endnote %}
 
+## Controlling runner software updates on self-hosted runners
+
+By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available.  If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released.  Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
+
+If you want to turn off automatic software updates and install software updates yourself, you can specify the `--disableupdate` parameter when starting the runner.  例:
+
+```shell
+./run.sh --disableupdate
+```
+
+If you disable automatic updates, you must still update your runner version regularly.  New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software.  The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
+
+If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available.  You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). 詳しい情報については、「[通知を設定する](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)」を参照してください。
+
+For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
+
+{% note %}
+
+**Note:** If you do not perform a software update within 30 days, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner.  In addition, if a critical security update is required, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner until it has been updated.
+
+{% endnote %}
+
 ## Using webhooks for autoscaling
 
 You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 1de5cdf6e1..8621853dcd 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -33,6 +33,38 @@ shortTitle: Monitor & troubleshoot
     * **Active**: The runner is currently executing a job.
     * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}.
 
+## Checking self-hosted runner network connectivity
+
+You can use the self-hosted runner application's `run` script with the `--check` parameter to check that a self-hosted runner can access all required network services on {% data variables.product.product_location %}.
+
+In addition to `--check`, you must provide two arguments to the script:
+
+* `--url` with the URL to your {% data variables.product.company_short %} repository, organization, or enterprise. For example, `--url https://github.com/octo-org/octo-repo`.
+* `--pat` with the value of a personal access token, which must have the `workflow` scope. For example, `--pat ghp_abcd1234`. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+For example:
+
+{% mac %}
+
+{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+
+{% endmac %}
+{% linux %}
+
+{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+
+{% endlinux %}
+{% windows %}
+
+```shell
+run.cmd --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
+```
+
+{% endwindows %}
+
+The script tests each service, and outputs either a `PASS` or `FAIL` for each one. If you have any failing checks, you can see more details on the problem in the log file for the check. The log files are located in the `_diag` directory where you installed the runner application, and the path of the log file for each check is shown in the console output of the script.
+
+If you have any failing checks, you should also verify that your self-hosted runner machine meets all the communication requirements. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)."
 
 ## Reviewing the self-hosted runner application log files
 
diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md
index 12dcd05619..8319ba548d 100644
--- a/translations/ja-JP/content/actions/index.md
+++ b/translations/ja-JP/content/actions/index.md
@@ -32,7 +32,6 @@ featuredLinks:
     - title: GitHub Actions in action – Karan MV
       href: 'https://www.youtube-nocookie.com/embed/4SWO0Pc76CU'
   videosHeading: GitHub Universe 2021 videos
-examples_source: data/product-examples/actions/code-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
 redirect_from:
   - /articles/automating-your-workflow-with-github-actions
diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
index 0cd202aaa4..7a31fd9ac9 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
@@ -393,7 +393,7 @@ The `steps` context contains information about the steps in the current job that
 | プロパティ名                                              | 種類       | 説明                                                                                                                                                                                                                                                                                 |
 | --------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `steps`                                             | `オブジェクト` | このコンテキストは、ジョブのステップごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。 This object contains all the properties listed below.                                                                                                                                                               |
-| `steps.<step_id>.outputs`                     | `オブジェクト` | ステップに定義された出力のセット。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions#outputs)」を参照してください。                                                                                                                            |
+| `steps.<step_id>.outputs`                     | `オブジェクト` | ステップに定義された出力のセット。 For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."                                                               |
 | `steps.<step_id>.conclusion`                  | `string` | [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)が適用された後に完了したステップの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 `continue-on-error`のステップが失敗すると、`outcome`は`failure`になりますが、最終的な`conclusion`は`success`になります。 |
 | `steps.<step_id>.outcome`                     | `string` | [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)が適用される前の完了したステップの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 `continue-on-error`のステップが失敗すると、`outcome`は`failure`になりますが、最終的な`conclusion`は`success`になります。 |
 | `steps.<step_id>.outputs.<output_name>` | `string` | 特定の出力の値。                                                                                                                                                                                                                                                                           |
diff --git a/translations/ja-JP/content/actions/learn-github-actions/expressions.md b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
index 2c71f16ac2..af3deef92d 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
@@ -268,9 +268,15 @@ jobs:
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 ## ステータスチェック関数
 
 `if` 条件では、次のステータスチェック関数を式として使用できます。 A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+{% else %}
+## Check Functions
+`if` 条件では、次のステータスチェック関数を式として使用できます。 A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+{% endif %}
 
 ### success
 
@@ -318,6 +324,7 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 ### Evaluate Status Explicitly
 
 Instead of using one of the methods above, you can evaluate the status of the job or composite action that is executing the step directly:
@@ -343,6 +350,7 @@ steps:
 ```
 
 This is the same as using `if: failure()` in a composite action step.
+{% endif %}
 
 ## オブジェクトフィルタ
 
diff --git a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
index ef41c90bec..1f4e787087 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -49,6 +49,8 @@ You can search and browse actions directly in your repository's workflow editor.
 
 You can add an action to your workflow by referencing the action in your workflow file. 
 
+You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
 ### Adding an action from {% data variables.product.prodname_marketplace %}
 
 An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
diff --git a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
index 786494ff08..8a754b65d2 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
@@ -255,3 +255,8 @@ To understand how billing works for {% data variables.product.prodname_actions %
 ## サポートへの連絡
 
 {% data reusables.github-actions.contacting-support %}
+
+## 参考リンク
+
+{% ifversion ghec or ghes or ghae %}
+- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 79832db60b..bb1173db96 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -18,16 +18,23 @@ shortTitle: Workflow billing & limits
 
 ## {% data variables.product.prodname_actions %}の支払いについて
 
+{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.actions-billing %} 詳細は「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 {% else %}
-GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
+GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。
 {% endif %}
 
+
+{% ifversion fpt or ghec %}
+
 ## 利用の可否
 
 {% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
 
+{% endif %}
+
 ## 使用制限
 
 {% ifversion fpt or ghec %}
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index 318a19da94..704e7cd535 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -63,7 +63,7 @@ Jenkinsは、_宣言的パイプライン_を管理するためにディレク
 | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                               | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                    | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                                                                                                                                                                                                                                                           |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                     | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore) <br> [<code>on.<pull_request\>.<branches\></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) |
 | [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                              | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | [Jenkinsのcron構文](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                              | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
index 4adb4d82c5..b86900fd20 100644
--- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
@@ -90,6 +90,9 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
+| pages         | read/write  | none | read |
+{%- endif %}
 | pull-requests | read/write  | none | read |
 | repository-projects | read/write | none | read |
 | security-events     | read/write | none | read |
diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
index d404b31b19..be53470b6a 100644
--- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
@@ -354,3 +354,50 @@ A workflow created in a repository can access the following number of secrets:
           run: cat $HOME/secrets/my_secret.json
   ```
 {% endraw %}
+
+
+## Storing Base64 binary blobs as secrets
+
+You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+
+{% note %}
+
+**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+
+{% endnote %}
+
+1. Use `base64` to encode your file into a Base64 string. 例:
+
+   ```
+   $ base64 -i cert.der -o cert.base64
+   ```
+
+1. Create a secret that contains the Base64 string. 例:
+
+   ```
+   $ gh secret set CERTIFICATE_BASE64 < cert.base64
+   ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
+   ```
+
+1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  例:
+
+   ```yaml
+   name: Retrieve Base64 secret
+   on:
+     push:
+       branches: [ octo-branch ]
+   jobs:
+     decode-secret:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: actions/checkout@v2
+         - name: Retrieve the secret and decode it to a file
+           env:
+             {% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
+           run: |
+             echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
+         - name: Show certificate information
+           run: |
+             openssl x509 -in cert.der -inform DER -text -noout
+   ```
+
diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
index ab54e41f45..53797cc901 100644
--- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -16,193 +16,9 @@ versions:
 shortTitle: ワークフローをトリガーするイベント
 ---
 
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## About events that trigger workflows
 
-## About workflow triggers
-
-Workflow triggers are events that cause a workflow to run. These events can be:
-
-- Events that occur in your workflow's repository
-- Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
-- Scheduled times
-- Manual
-
-For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.
-
-Workflow triggers are defined with the `on` key. 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#on)」を参照してください。
-
-ワークフローの実行がトリガーされるには、以下のステップが生じます。
-
-1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
-1. {% data variables.product.product_name %} searches the `.github/workflows` directory in your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
-
-1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
-
-  Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. ワークフローを実行すると、{% data variables.product.product_name %} はランナー環境において `GITHUB_SHA` (コミット SHA) および `GITHUB_REF` (Git ref) 環境変数を設定します。 詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。
-
-### Triggering a workflow from a workflow
-
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
-
-If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
-
-For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
-
-```yaml
-on:
-  issues:
-    types:
-      - opened
-
-jobs:
-  label_issue:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.MY_TOKEN }}{% endraw %}
-          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
-        run: |
-          gh issue edit $ISSUE_URL --add-label "triage"
-```
-
-Conversely, the following workflow uses `GITHUB_TOKEN` to add a label to an issue. It will not trigger any workflows that run when a label is added.
-
-```yaml
-on:
-  issues:
-    types:
-      - opened
-
-jobs:
-  label_issue:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
-        run: |
-          gh issue edit $ISSUE_URL --add-label "triage"
-```
-
-## Using events to trigger workflows
-
-Use the `on` key to specify what events trigger your workflow. For more information about events you can use, see "[Available events](#available-events)" below.
-
-{% data reusables.github-actions.actions-on-examples %}
-
-## Using event information
-
-Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
-
-### Viewing all properties of an event
-
-Reference the webhook event documentation for common properties and example payloads. 詳しい情報については、「[webhook イベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)」を参照してください。
-
-You can also print the entire `github.event` context to see what properties are available for the event that triggered your workflow:
-
-```yaml
-jobs:
-  print_context:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          EVENT_CONTEXT: {% raw %}${{ toJSON(github.event) }}{% endraw %}
-        run: |
-          echo $EVENT_CONTEXT
-```
-
-### Accessing and using event properties
-
-You can use the `github.event` context in your workflow. For example, the following workflow runs when a pull request that changes `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**` is opened. If the pull request author (`github.event.pull_request.user.login`) is not `octobot` or `dependabot[bot]`, then the workflow uses the {% data variables.product.prodname_cli %} to label and comment on the pull request (`github.event.pull_request.number`).
-
-```yaml
-on:
-  pull_request:
-    types:
-      - opened
-    paths:
-      - '.github/workflows/**'
-      - '.github/CODEOWNERS'
-      - 'package*.json'
-
-jobs:
-  triage:
-    if: >-
-      github.event.pull_request.user.login != 'octobot' &&
-      github.event.pull_request.user.login != 'dependabot[bot]'
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Comment about changes we can't accept"
-        env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-          PR: {% raw %}${{ github.event.pull_request.html_url }}{% endraw %}
-        run: |
-          gh pr edit $PR --add-label 'invalid'
-          gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
-```
-
-For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
-
-## Further controlling how your workflow will run
-
-If you want more granular control than events, event activity types, or event filters provide, you can use conditionals{% ifversion fpt or ghae or ghes > 3.1 or ghec %} and environments{% endif %} to control whether individual jobs or steps in your workflow will run.
-
-### Using conditionals
-
-You can use conditionals to further control whether jobs or steps in your workflow will run. For example, if you want the workflow to run when a specific label is added to an issue, you can trigger on the `issues labeled` event activity type and use a conditional to check what label triggered the workflow. The following workflow will run when any label is added to an issue in the workflow's repository, but the `run_if_label_matches` job will only execute if the label is named `bug`.
-
-```yaml
-on:
-  issues:
-    types:
-      - labeled
-
-jobs:
-  run_if_label_matches:
-    if: github.event.label.name == 'bug'
-    runs-on: ubuntu-latest
-    steps:
-      - run: echo 'The label was bug'
-```
-
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Using environments to manually trigger workflow jobs
-
-If you want to manually trigger a specific job in a workflow, you can use an environment that requires approval from a specific team or user. First, configure an environment with required reviewers. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." Then, reference the environment name in a job in your workflow using the `environment:` key. Any job referencing the environment will not run until at least one reviewer approves the job.
-
-For example, the following workflow will run whenever there is a push to main. The `build` job will always run. The `publish` job will only run after the `build` job successfully completes (due to `needs: [build]`) and after all of the rules (including required reviewers) for the environment called `production` pass (due to `environment: production`).
-
-```yaml
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: build
-        echo 'building'
-
-  publish:
-    needs: [build]
-    runs-on: ubuntu-latest
-    environment: production
-    steps:
-      - name: publish
-        echo 'publishing'
-```
-
-{% note %}
-
-{% data reusables.gated-features.environments %}
-
-{% endnote %}
-{% endif %}
+Workflow triggers are events that cause a workflow to run. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
 
 ## Available events
 
@@ -794,7 +610,7 @@ jobs:
 
 #### Running your workflow based on the head or base branch of a pull request
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)」を参照してください。
 
 For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
 
@@ -841,7 +657,7 @@ jobs:
 
 #### Running your workflow based on files changed in a pull request
 
-You can also configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can also configure your workflow to run when a pull request changes specific files. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)」を参照してください。
 
 For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
 
@@ -978,7 +794,7 @@ on:
 
 #### Running your workflow based on the head or base branch of a pull request
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)」を参照してください。
 
 For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
 
@@ -1025,7 +841,7 @@ jobs:
 
 #### Running your workflow based on files changed in a pull request
 
-You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)」を参照してください。
 
 For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
 
@@ -1082,7 +898,7 @@ on:
 
 #### Running your workflow only when a push to specific branches occurs
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)」を参照してください。
 
 For example, this workflow will run when someone pushes to `main` or to a branch that starts with `releases/`.
 
@@ -1113,7 +929,7 @@ on:
 
 #### Running your workflow only when a push of specific tags occurs
 
-You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags or are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags or are pushed. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)」を参照してください。
 
 For example, this workflow will run when someone pushes a tag that starts with `v1.`.
 
@@ -1126,7 +942,7 @@ on:
 
 #### Running your workflow only when a push affects specific files
 
-You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a push to specific files occurs. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a push to specific files occurs. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)」を参照してください。
 
 For example, this workflow will run when someone pushes a change to a JavaScript file (`.js`):
 
@@ -1168,7 +984,7 @@ on:
 
 {% data reusables.github-actions.branch-requirement %}
 
-Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. For more information, see "[{% data variables.product.prodname_registry %} Documentation](/packages)."
+Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. 詳しい情報については、「[{% data variables.product.prodname_registry %} のドキュメント](/packages)」を参照してください。
 
 たとえば、パッケージが`published`されたときにワークフローを実行できます。
 
@@ -1220,7 +1036,7 @@ on:
 
 {% data reusables.github-actions.branch-requirement %}
 
-You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.product_name %}. 詳細については、「[リポジトリディスパッチ イベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。
+{% data variables.product.product_name %} の外部で生じるアクティビティのためにワークフローをトリガーしたい場合、{% data variables.product.product_name %} API を使って、[`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) と呼ばれる webhook イベントをトリガーできます。 詳細については、「[リポジトリディスパッチ イベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。
 
 When you make a request to create a `repository_dispatch` event, you must specify an `event_type` to describe the activity type. By default, all `repository_dispatch`  activity types trigger a workflow to run. You can use the `types` keyword to limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload.
 
@@ -1371,7 +1187,7 @@ on:
 | --------------------------- | ---------- | --------------------------- | --------------------------- |
 | Same as the caller workflow | n/a        | Same as the caller workflow | Same as the caller workflow |
 
-`workflow_call` is used to indicate that a workflow can be called by another workflow. When a workflow is triggered with the `workflow_call` event, the event playload in the called workflow is the same event payload from the calling workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+`workflow_call` is used to indicate that a workflow can be called by another workflow. When a workflow is triggered with the `workflow_call` event, the event payload in the called workflow is the same event payload from the calling workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 
 The example below only runs the workflow when it's called from another workflow:
 
@@ -1395,7 +1211,7 @@ on: workflow_dispatch
 
 #### Providing inputs
 
-カスタム定義の入力プロパティ、デフォルトの入力値、イベントに必要な入力をワークフローで直接設定できます。 When you trigger the event, you can provide the `ref` and any `inputs`. ワークフローが実行されると、`github.event.inputs` コンテキストの入力値にアクセスできます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
+カスタム定義の入力プロパティ、デフォルトの入力値、イベントに必要な入力をワークフローで直接設定できます。 When you trigger the event, you can provide the `ref` and any `inputs`. ワークフローが実行されると、 `github.event.inputs` コンテキスト内の入力値にアクセスできます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
 This example defines inputs called `logLevel`, `tags`, and `environment`. You pass values for these inputs to the workflow when you run it. This workflow then prints the values to the log, using the `github.event.inputs.logLevel`, `github.event.inputs.tags`, and  `github.event.inputs.environment` context properties.
diff --git a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
index 8c8a23aeaa..5c84e808d0 100644
--- a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
@@ -34,6 +34,8 @@ If you reuse a workflow from a different repository, any actions in the called w
 
 When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
 
+You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
 ### Reusable workflows and starter workflows
 
 Starter workflows allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Within a starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
@@ -110,7 +112,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
        runs-on: ubuntu-latest
        environment: production
        steps:
-         - uses: ./.github/actions/my-action@v1
+         - uses: ./.github/actions/my-action
            with:
              username: ${{ inputs.username }}
              token: ${{ secrets.envPAT }}
@@ -151,7 +153,7 @@ jobs:
     name: Pass input and secrets to my-action
     runs-on: ubuntu-latest
     steps:
-      - uses: ./.github/actions/my-action@v1
+      - uses: ./.github/actions/my-action
         with:
           username: ${{ inputs.username }}
           token: ${{ secrets.token }}
diff --git a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
index 9b45107b94..fb4733ce84 100644
--- a/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/ja-JP/content/actions/using-workflows/triggering-a-workflow.md
@@ -12,36 +12,242 @@ topics:
   - Workflows
   - CI
   - CD
-miniTocMaxHeadingLevel: 4
+miniTocMaxHeadingLevel: 3
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 概要
+## About workflow triggers
 
-{% data reusables.actions.workflows.section-triggering-a-workflow %}
+Workflow triggers are events that cause a workflow to run. These events can be:
 
-## Defining event types
+- Events that occur in your workflow's repository
+- Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
+- Scheduled times
+- Manual
 
-{% data reusables.actions.workflows.section-triggering-a-workflow-types %}
+For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.
 
-## 特定のブランチをターゲットにする
+Workflow triggers are defined with the `on` key. 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#on)」を参照してください。
+
+ワークフローの実行がトリガーされるには、以下のステップが生じます。
+
+1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
+1. {% data variables.product.product_name %} searches the `.github/workflows` directory in your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
+1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
+
+  Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. ワークフローを実行すると、{% data variables.product.product_name %} はランナー環境において `GITHUB_SHA` (コミット SHA) および `GITHUB_REF` (Git ref) 環境変数を設定します。 詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。
+
+### Triggering a workflow from a workflow
+
+{% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+
+If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.MY_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+Conversely, the following workflow uses `GITHUB_TOKEN` to add a label to an issue. It will not trigger any workflows that run when a label is added.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+## Using events to trigger workflows
+
+Use the `on` key to specify what events trigger your workflow. For more information about events you can use, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+
+### Using a single event
+
+{% data reusables.github-actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.github-actions.on-multiple-example %}
+
+### Using activity types and filters with multiple events
+
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+
+## Using event activity types
+
+{% data reusables.github-actions.actions-activity-types %}
+
+## Using filters
+
+{% data reusables.github-actions.actions-filters %}
+
+### Using filters to target specific branches for pull request events
 
 {% data reusables.actions.workflows.section-triggering-a-workflow-branches %}
 
-## Running on specific branches or tags
+### Using filters to target specific branches or tags for push events
 
 {% data reusables.actions.workflows.section-run-on-specific-branches-or-tags %}
 
-## Specifying which branches the workflow can run on
-
-{% data reusables.actions.workflows.section-specifying-branches %}
-
-## Using specific file paths
+### Using filters to target specific paths for pull request or push events
 
 {% data reusables.actions.workflows.section-triggering-a-workflow-paths %}
 
-## Using a schedule
+### Using filters to target specific branches for workflow run events
 
-{% data reusables.actions.workflows.section-triggering-a-workflow-schedule %}
+{% data reusables.actions.workflows.section-specifying-branches %}
+
+## Defining inputs for manually triggered workflows
+
+{% data reusables.github-actions.workflow-dispatch-inputs %}
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+## Defining inputs, outputs, and secrets for reusable workflows
+
+You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+
+{% endif %}
+
+## Using event information
+
+Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
+
+### Viewing all properties of an event
+
+Reference the webhook event documentation for common properties and example payloads. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+You can also print the entire `github.event` context to see what properties are available for the event that triggered your workflow:
+
+```yaml
+jobs:
+  print_context:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          EVENT_CONTEXT: {% raw %}${{ toJSON(github.event) }}{% endraw %}
+        run: |
+          echo $EVENT_CONTEXT
+```
+
+### Accessing and using event properties
+
+You can use the `github.event` context in your workflow. For example, the following workflow runs when a pull request that changes `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**` is opened. If the pull request author (`github.event.pull_request.user.login`) is not `octobot` or `dependabot[bot]`, then the workflow uses the {% data variables.product.prodname_cli %} to label and comment on the pull request (`github.event.pull_request.number`).
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    paths:
+      - '.github/workflows/**'
+      - '.github/CODEOWNERS'
+      - 'package*.json'
+
+jobs:
+  triage:
+    if: >-
+      github.event.pull_request.user.login != 'octobot' &&
+      github.event.pull_request.user.login != 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: "Comment about changes we can't accept"
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          PR: {% raw %}${{ github.event.pull_request.html_url }}{% endraw %}
+        run: |
+          gh pr edit $PR --add-label 'invalid'
+          gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
+```
+
+For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+## Further controlling how your workflow will run
+
+If you want more granular control than events, event activity types, or event filters provide, you can use conditionals{% ifversion fpt or ghae or ghes > 3.1 or ghec %} and environments{% endif %} to control whether individual jobs or steps in your workflow will run.
+
+### Using conditionals
+
+You can use conditionals to further control whether jobs or steps in your workflow will run. For example, if you want the workflow to run when a specific label is added to an issue, you can trigger on the `issues labeled` event activity type and use a conditional to check what label triggered the workflow. The following workflow will run when any label is added to an issue in the workflow's repository, but the `run_if_label_matches` job will only execute if the label is named `bug`.
+
+```yaml
+on:
+  issues:
+    types:
+      - labeled
+
+jobs:
+  run_if_label_matches:
+    if: github.event.label.name == 'bug'
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo 'The label was bug'
+```
+
+For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+
+### Using environments to manually trigger workflow jobs
+
+If you want to manually trigger a specific job in a workflow, you can use an environment that requires approval from a specific team or user. First, configure an environment with required reviewers. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." Then, reference the environment name in a job in your workflow using the `environment:` key. Any job referencing the environment will not run until at least one reviewer approves the job.
+
+For example, the following workflow will run whenever there is a push to main. The `build` job will always run. The `publish` job will only run after the `build` job successfully completes (due to `needs: [build]`) and after all of the rules (including required reviewers) for the environment called `production` pass (due to `environment: production`).
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: build
+        echo 'building'
+
+  publish:
+    needs: [build]
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: publish
+        echo 'publishing'
+```
+
+{% note %}
+
+{% data reusables.gated-features.environments %}
+
+{% endnote %}
+{% endif %}
+
+## Available events
+
+For a full list of available events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 7fd53542cc..67d67ace64 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -92,7 +92,7 @@ core.setOutput('SELECTED_COLOR', 'green');
 
 アクションの出力パラメータを設定します。
 
-あるいは、出力パラメータをアクションのメタデータファイル中で宣言することもできます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions#outputs)」を参照してください。
+あるいは、出力パラメータをアクションのメタデータファイル中で宣言することもできます。 For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
 
 ### サンプル
 
@@ -292,7 +292,7 @@ Only the second `set-output` and `echo` workflow commands are included in the lo
 
 `save-state`コマンドを使って、ワークフローの`pre:`あるいは`post:`アクションと共有するための環境変数を作成できます。 たとえば、`pre:`アクションでファイルを作成し、そのファイルの場所を`main:`アクションに渡し、`post:`アクションを使ってそのファイルを削除できます。 あるいは、ファイルを`main:`アクションで作成し、そのファイルの場所を`post:`アクションに渡し、`post:`アクションを使ってそのファイルを削除することもできます。
 
-複数の`pre:`あるいは`post:`アクションがある場合、保存された値にアクセスできるのは`save-state`が使われたアクションの中でのみです。 `post:`アクションに関する詳しい情報については「[{% data variables.product.prodname_actions %}のためのメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions#post)」を参照してください。
+複数の`pre:`あるいは`post:`アクションがある場合、保存された値にアクセスできるのは`save-state`が使われたアクションの中でのみです。 `post:`アクションに関する詳しい情報については「[{% data variables.product.prodname_actions %}のためのメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions#runspost)」を参照してください。
 
 `save-state`コマンドはアクション内でしか実行できず、YAMLファイルでは利用できません。 保存された値は、`STATE_`プレフィックス付きで環境変数として保存されます。
 
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 530efadfed..54f330213b 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -149,7 +149,7 @@ jobs:
 
     steps:
       - name: Pass the received secret to an action
-        uses: ./.github/actions/my-action@v1
+        uses: ./.github/actions/my-action
         with:
           token: ${{ secrets.access-token }}
 ```
@@ -171,42 +171,7 @@ A boolean specifying whether the secret must be supplied.
 
 ## `on.workflow_dispatch.inputs`
 
-When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
-
-The triggered workflow receives the inputs in the `github.event.inputs` context. 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。
-
-### サンプル
-```yaml
-on:
-  workflow_dispatch:
-    inputs:
-      logLevel:
-        description: 'Log level'
-        required: true
-        default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
-        type: choice
-        options:
-        - info
-        - warning
-        - debug {% endif %}
-      tags:
-        description: 'Test scenario tags'
-        required: false {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
-        type: boolean
-      environment:
-        description: 'Environment to run tests against'
-        type: environment
-        required: true {% endif %}
-
-jobs:
-  print-tag:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Print the input tag to STDOUT
-        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
-```
-
+{% data reusables.github-actions.workflow-dispatch-inputs %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `permissions`
@@ -1008,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.<push>
 | `'**'`                                                  | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。                          | `all/the/branches`<br/><br/>`every/tag`                                                                   |
 | `'*feature'`                                            | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。                                      | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
 | `v2*`                                                   | `v2`で始めるブランチ及びタグ名にマッチします。                                                                      | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
-| `v[12].[0-9]+.[0-9]+`                                   | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングブランチとタグにマッチします。                                             | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
+| `v[12].[0-9]+.[0-9]+`                                   | Matches all semantic versioning branches and tags with major version 1 or 2.                   | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
 ### ファイルパスにマッチするパターン
 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
index ae5dbb6d35..223e4fe978 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -38,6 +38,8 @@ SSL が有効な場合、{% data variables.product.prodname_ghe_server %} アプ
 
 ## カスタムのTLS証明書のアップロード
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
@@ -67,6 +69,8 @@ Let's Encryptを使ったTLS証明書管理の自動化を有効にすると、{
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 7a347ea3ce..afe9132dfc 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -136,5 +136,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 You can use these additional options with `ghe-restore` command:
-- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - The `-s` flag allows you to select a different backup snapshot.
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index e0987ad337..8f9f359c87 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -88,8 +88,7 @@ settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-all
 4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery).
 5. When the test email succeeds, at the bottom of the page, click **Save settings**.
 ![Save settings button](/assets/images/enterprise/management-console/save-settings.png)
-6. Wait for the configuration run to complete.
-![Configuring your instance](/assets/images/enterprise/management-console/configuration-run.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 ## Configuring DNS and firewall settings to allow incoming emails
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index 6033153a5d..f041be2db2 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -47,7 +47,7 @@ topics:
 
 ## collectd データの `ghe-export-graphs`でのエクスポート
 
-`ghe-export-graphs` のコマンドラインツールは、`collectd` が RRD データベースに保存するデータをエクスポートします。 このコマンドは、データを XML にして、1つのTAR書庫（.tgz）にエクスポートします。
+`ghe-export-graphs` のコマンドラインツールは、`collectd` が RRD データベースに保存するデータをエクスポートします。 This command turns the data into XML and exports it into a single tarball (`.tgz`).
 
 その主な用途は、Support Bundleを一括ダウンロードする必要なく、{% data variables.contact.contact_ent_support %}のチームに仮想マシンのパフォーマンスに関するデータ提供することです。 定期的なバックアップエクスポートに含めてはなりません。また、その逆のインポートもありません。 {% data variables.contact.contact_ent_support %}に連絡したとき、問題解決を容易にするため、このデータが必要となる場合があります。
 
diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index eeae6fb8a8..be6dc809eb 100644
--- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -52,9 +52,11 @@ If you use Docker container actions or service containers in your workflows, you
 
 If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
 
-## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname
+## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
 
-If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
 
 You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures:
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
new file mode 100644
index 0000000000..9a603d9b4e
--- /dev/null
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -0,0 +1,42 @@
+---
+title: About GitHub Actions for enterprises
+shortTitle: GitHub Actionsについて
+intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
+
+| Task                                                                  | 詳細情報                                                                                                                                                                   |
+| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Automatically test and build your application                         | [継続的インテグレーションについて](/actions/automating-builds-and-tests/about-continuous-integration)                                                                                  |
+| Deploy your application                                               | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)"                                                                     |
+| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)"                               |
+| Automate your project management tasks                                | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+
+{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
+
+{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
+{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
+
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. 詳しい情報については「[アクションの発見とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
+
+{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+
+
+To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
+
+## 参考リンク
+
+- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
+- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 10d115294f..116c614f7a 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -9,6 +9,7 @@ topics:
   - Enterprise
   - Actions
 children:
+  - /about-github-actions-for-enterprises
   - /introducing-github-actions-to-your-enterprise
   - /migrating-your-enterprise-to-github-actions
   - /getting-started-with-github-actions-for-github-enterprise-cloud
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 07d53a87c4..ff70e83ebd 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -14,7 +14,7 @@ topics:
 
 ## About {% data variables.product.prodname_actions %} for enterprises
 
-{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
 
 ![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
 
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/ja-JP/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index 40e9dd0139..adfee2348c 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -178,7 +178,7 @@ LDAP Sync が有効化されると、サイト管理者と Organization のオ
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 3. 左のサイドバーで**LDAP users（LDAPユーザ）**をクリックしてください。 ![LDAP ユーザタブ](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. ユーザを検索するには、完全なユーザ名もしくはユーザ名の一部を入力し、**Search（検索）**をクリックしてください。 検索結果に該当するユーザが表示されます。 該当するユーザがいなければ、**Create（作成）**をクリックして新しいユーザアカウントをプロビジョニングできます。 ![LDAP検索](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
+4. ユーザを検索するには、完全なユーザ名もしくはユーザ名の一部を入力し、**Search（検索）**をクリックしてください。 検索結果に該当するユーザが表示されます。 該当するユーザがいなければ、**Create（作成）**をクリックして新しいユーザアカウントをプロビジョニングできます。 ![LDAP検索](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg)
 
 ## LDAPアカウントの更新
 
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index f818cd95b0..a3b6cec219 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -47,6 +47,7 @@ Configuring {% data variables.product.prodname_emus %} for SAML single-sign on a
 | ------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
 | Active Directory フェデレーションサービス (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
 | Azure Active Directory (Azure AD)     | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| Okta                                  | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
 | OneLogin                              | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | PingOne                               | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | Shibboleth                            | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index 9066ea48a9..334b66bbaf 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -15,8 +15,6 @@ redirect_from:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
-
 ## Enterprise アカウントの SAML シングルサインオンについて
 
 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md
index e413a0303e..e660dafc6e 100644
--- a/translations/ja-JP/content/admin/index.md
+++ b/translations/ja-JP/content/admin/index.md
@@ -97,12 +97,14 @@ featuredLinks:
     - '{% ifversion ghes %}/admin/installation{% endif %}'
     - '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
     - '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
     - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
     - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
+    - /admin/configuration/configuring-github-connect/managing-github-connect
     - /admin/enterprise-support/about-github-enterprise-support
   videos:
     - title: GitHub in the Enterprise – Maya Ross
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 25b78cca2d..1a27917660 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -40,12 +40,12 @@ Azure で{% data variables.product.product_location %} を起動する前に、O
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. 最新の {% data variables.product.prodname_ghe_server %} アプライアンスイメージを見つけます。 `vm image list` コマンドの詳細については、Microsoft のドキュメントの「[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)」を参照してください。
+1. 最新の {% data variables.product.prodname_ghe_server %} アプライアンスイメージを見つけます。 For more information about the `vm image list` command, see "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. 見つけたアプライアンスイメージを使用して新しい VM を作成します。 詳しい情報については、Microsoftドキュメンテーションの「[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)」を参照してください。
+2. 見つけたアプライアンスイメージを使用して新しい VM を作成します。 For more information, see "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
 
   VM の名前、リソースグループ、VM のサイズ、優先する Azure リージョンの名前、前の手順でリストしたアプライアンスイメージ VM の名前、およびプレミアムストレージ用のストレージ SKU についてのオプションを渡します。 リソースグループに関する詳しい情報については、Microsoft ドキュメンテーションの「[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)」を参照してください。
 
@@ -53,7 +53,7 @@ Azure で{% data variables.product.product_location %} を起動する前に、O
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. 必要なポートを開くように VM でセキュリティを設定します。 詳しい情報については、Microsoft ドキュメンテーションの「[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)」を参照してください。 どのポートを開く必要があるかを判断するための各ポートの説明については、以下の表を参照してください。
+3. 必要なポートを開くように VM でセキュリティを設定します。 For more information, see "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. どのポートを開く必要があるかを判断するための各ポートの説明については、以下の表を参照してください。
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
@@ -63,7 +63,7 @@ Azure で{% data variables.product.product_location %} を起動する前に、O
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
+4. 暗号化されていない新しいデータディスクを作成してVMにアタッチし、ユーザライセンス数に応じてサイズを設定してください。 For more information, see "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
 
   VM の名前 (`ghe-acme-corp` など)、リソースグループ、プレミアムストレージ SKU、ディスクのサイズ (`100` など)、および作成する VHD の名前についてのオプションを渡します。
 
@@ -79,7 +79,7 @@ Azure で{% data variables.product.product_location %} を起動する前に、O
 
 ## {% data variables.product.prodname_ghe_server %} 仮想マシンを設定する
 
-1. VM を設定する前に、VMがReadyRole ステータスになるのを待つ必要があります。 VM のステータスを `vm list` コマンドで確認します。 詳しい情報については、Microsoft ドキュメンテーションの「[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)」を参照してください。
+1. VM を設定する前に、VMがReadyRole ステータスになるのを待つ必要があります。 VM のステータスを `vm list` コマンドで確認します。 For more information, see "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
diff --git a/translations/ja-JP/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/ja-JP/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
new file mode 100644
index 0000000000..d9b852ee0c
--- /dev/null
+++ b/translations/ja-JP/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your enterprise
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Enterprise owners can access compliance reports for the enterprise.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## 参考リンク
+
+- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
diff --git a/translations/ja-JP/content/admin/overview/index.md b/translations/ja-JP/content/admin/overview/index.md
index a7e69f697e..ac6ac58d23 100644
--- a/translations/ja-JP/content/admin/overview/index.md
+++ b/translations/ja-JP/content/admin/overview/index.md
@@ -15,6 +15,7 @@ children:
   - /system-overview
   - /about-the-github-enterprise-api
   - /creating-an-enterprise-account
+  - /accessing-compliance-reports-for-your-enterprise
 ---
 
 詳しい情報または {% data variables.product.prodname_enterprise %} の購入については [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) を参照してください。
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 1e636d370e..0e0d42f008 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -100,6 +100,10 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 1e08869a76..11b1ab119f 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -146,9 +146,8 @@ CAを削除すると、元に戻すことはできません。 同じCAを使用
 {% data reusables.organizations.delete-ssh-ca %}
 
 {% ifversion ghec or ghae %}
-
 ## 参考リンク
 
-- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
-
+- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
 {% endif %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 48b09b3704..182e146c8e 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -90,6 +90,9 @@ The `$GITHUB_VIA` variable is available in the pre-receive hook environment when
 | <pre>git refs delete api</pre> | Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation |
 | <pre>git refs update api</pre> | Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation |
 | <pre>git repo contents api</pre> | Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation |
+{%- ifversion ghes > 3.0 %}
+| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
 | <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" |
 | <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
 | <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" |
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index 4eca1ad2c1..9a7ddb4056 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -9,6 +9,7 @@ redirect_from:
 intro: 'Team が作成されると、Organization の管理者はユーザを {% data variables.product.product_location %} から Team に追加し、どのリポジトリにアクセスできるようにするかを決定できます。'
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -30,8 +31,12 @@ topics:
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
+{% ifversion ghes %}
+
 ## TeamのLDAPグループへのマッピング（たとえばLDAP Syncをユーザ認証に使って）
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
 LDAPグループに同期されているTeamに新しいメンバーを追加するには、そのユーザをLDAPグループのメンバーとして追加するか、LDAPの管理者に連絡してください。
+
+{% endif %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
index e90cbe2535..93e7b879d7 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
@@ -7,6 +7,7 @@ redirect_from:
   - /admin/user-management/continuous-integration-using-jenkins
 versions:
   ghes: '*'
+  ghae: '*'
 type: reference
 topics:
   - CI
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
index 52334965f2..e638566bb1 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/creating-teams
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -32,6 +33,8 @@ A prudent combination of teams is a powerful way to control repository access. F
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
 
+{% ifversion ghes %}
+
 ## Creating teams with LDAP Sync enabled
 
 Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
@@ -60,3 +63,5 @@ You must be a site admin and an organization owner to create a team with LDAP sy
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 8bc90cf1ec..27c57f4e9c 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
 title: Managing projects using Jira
-intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.'
+intro: 'You can integrate Jira with {% data variables.product.product_name %} for project management.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira
   - /enterprise/admin/articles/project-management-using-jira
@@ -10,6 +10,7 @@ redirect_from:
   - /admin/user-management/managing-projects-using-jira
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
index 1c079018a3..1b962a0360 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/removing-users-from-teams-and-organizations
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -25,6 +26,8 @@ Organizationのメンバーを削除できるのは、オーナーもしくはTe
 
 ## Teamメンバーの削除
 
+{% ifversion ghes %}
+
 {% warning %}
 
 **ノート：**{% data reusables.enterprise_management_console.badge_indicator %}
@@ -33,6 +36,8 @@ LDAPグループに同期しているTeamの既存メンバーを削除するに
 
 {% endwarning %}
 
+{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index adf3ed4820..d902b4b154 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -15,7 +15,7 @@ shortTitle: Manage support entitlements
 
 People with support entitlements for your enterprise account can use the support portal to open, view, and comment on support tickets associated with the enterprise account.
 
-Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to members of organizations owned by their enterprise account.
+Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to up to 20 additional members of organizations owned by their enterprise account.
 
 ## Adding a support entitlement to an enterprise member
 
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index b508e1d34b..c464510264 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -26,7 +26,7 @@ Git プッシュ操作はすべてログに記録されます。 詳しい情報
 {% ifversion ghes %}
 ## システムイベント
 
-すべてのプッシュとプルを含む監査されたすべてのシステムイベントは、`/var/log/github/audit.log` に記録されます。 ログは 24 時間ごとに自動的に交換され、7 日間保持されます。
+All audited system events are logged to `/var/log/github/audit.log`. ログは 24 時間ごとに自動的に交換され、7 日間保持されます。
 
 Support Bundle にはシステムログが含まれています。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Support にデータを提供する](/admin/enterprise-support/providing-data-to-github-support)」を参照してください。
 
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 0c28a9892c..937cba2241 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -8,6 +8,7 @@ redirect_from:
   - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
   - /github/authenticating-to-github/creating-a-personal-access-token
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
+  - /github/extending-github/git-automation-with-oauth-tokens
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b549916188..a8acb33c40 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,11 @@ shortTitle: デプロイキー
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
 3. 左サイドバーで [**Deploy keys**] をクリックします。 ![デプロイキーの設定](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
 4. [Deploy keys] ページで、自分のアカウントに関連付けられているデプロイ キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効なデプロイ キーがある場合は、[**Approve**] をクリックします。 ![デプロイキーのリスト](/assets/images/help/settings/settings-deploy-key-review.png)
 
 詳しい情報については、「[デプロイキーを管理する](/guides/managing-deploy-keys)」を参照してください。
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 517eec4f18..ca148abe16 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -22,12 +22,10 @@ shortTitle: セキュリティ ログ
 The security log lists all actions performed within the last 90 days.
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghae or ghes or ghec %}
-2. ユーザ設定サイドバーで [**Security log**] をクリックします。 ![セキュリティログのタブ](/assets/images/help/settings/audit-log-tab.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else %}
-{% data reusables.user_settings.security %}
-3. [Security history] の下に、自分のログが表示されます。 ![セキュリティ ログ](/assets/images/help/settings/user_security_log.png)
-4. エントリをクリックして、イベントに関する詳細情報を表示します。 ![セキュリティ ログ](/assets/images/help/settings/user_security_history_action.png)
+1. ユーザ設定サイドバーで [**Security log**] をクリックします。 ![セキュリティログのタブ](/assets/images/help/settings/audit-log-tab.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
index 9e34b7136f..e27c854f3e 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -33,7 +33,7 @@ $ ssh -T -p 443 git@ssh.github.com
 
 If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.product.product_location %} to run through that server and port.
 
-ssh 設定でこれを設定するには、`~/.ssh/config` のファイルを編集して、このセクションを追加してください:
+To set this in your SSH confifguration file, edit the file at `~/.ssh/config`, and add this section:
 
 ```
 Host {% data variables.command_line.codeblock %}
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 932d60a23b..76511c67fa 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -37,6 +37,10 @@ If you want to view an overview of your subscription and usage for {% data varia
 
 ## Enterprise アカウントのプランおよび利用状況を表示する
 
+You can view the subscription and usage for your enterprise and download a file with license details.
+
+{% data reusables.billing.license-statuses %}
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/about-billing-on-github.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
index a5edc4568c..2ebaa2f773 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
@@ -36,7 +36,7 @@ OrganizationあるいはEnterpriseのオーナーは、設定のコンテキス
 {% data reusables.user_settings.access_settings %}
 1. ページの上部で、ユーザ名の右の**Switch to another account（他のアカウントに切り替え）** ![コンテキストスイッチャーボタン](/assets/images/help/settings/context-switcher-button.png)
 1. 切り替えたいアカウントの名前を入力し始め、そのアカウントの名前をクリックしてください。 ![コンテキストスイッチャーメニュー](/assets/images/help/settings/context-switcher-menu.png)
-1. 左のサイドバーで**Billing & plans（支払とプラン）**をクリックしてください。 ![設定サイドバーの支払とプラン](/assets/images/help/organizations/billing-settings.png)
+1. In the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
 
 ## 参考リンク
 
diff --git a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
index 47a5ccfa1e..a630ca1f69 100644
--- a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
+++ b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
@@ -30,6 +30,10 @@ You can view license usage for {% data variables.product.prodname_ghe_server %}
 
 ## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}
 
+You can view the license usage for your enterprise and download a file with license details.
+
+{% data reusables.billing.license-statuses %}
+
 {% ifversion ghec %}
 
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
new file mode 100644
index 0000000000..2e6daf26d3
--- /dev/null
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
@@ -0,0 +1,119 @@
+---
+title: About code scanning alerts
+intro: 'Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About alerts from {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+## About alert details
+
+Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
+
+If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+
+When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+
+### About severity levels
+
+Alert severity levels may be `Error`, `Warning`, or `Note`.
+
+If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+### About security severity levels
+
+{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
+
+To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
+
+By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+### About labels for alerts that are not found in application code
+
+{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
+
+- **Generated**: Code generated by the build process
+- **Test**: Test code
+- **Library**: Library or third-party code
+- **Documentation**: Documentation
+
+{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
+
+Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
+
+![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
+
+On the alert page, you can see that the filepath is marked as library code (`Library` label).
+
+![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
+
+{% if codeql-ml-queries %}
+
+## About experimental alerts
+
+{% data reusables.code-scanning.beta-codeql-ml-queries %}
+
+In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
+
+![Code scanning experimental alert in list](/assets/images/help/repository/code-scanning-experimental-alert-list.png)
+
+### Benefits of using machine learning models to extend queries
+
+Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
+
+Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
+
+{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
+
+### Alerts identified using machine learning
+
+Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
+
+![Code scanning experimental alert details](/assets/images/help/repository/code-scanning-experimental-alert-show.png)
+
+## Enabling experimental alerts
+
+The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you update your workflow to run an additional query suite this will increase the analysis time.
+
+``` yaml
+- uses: github/codeql-action/init@v1
+  with:
+    # Run extended queries including queries using machine learning
+    queries: security-extended
+```
+
+For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+## Disabling experimental alerts
+
+The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
+
+- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
+- Specify details of the repositories or organizations that are affected
+- Request an escalation to engineering
+
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index fb05626d65..70303ae4d7 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -43,7 +43,7 @@ There are two main ways to use {% data variables.product.prodname_codeql %} anal
 
 ## About {% data variables.product.prodname_codeql %} queries
 
-{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://codeql.github.com/) on the {% data variables.product.prodname_codeql %} website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
 
 You can run additional queries as part of your code scanning analysis. 
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index 6115cb843c..778ceed4b3 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -18,7 +18,6 @@ topics:
   - Code scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index eafbc64c0b..af256d5d03 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -24,7 +24,7 @@ topics:
   - Python
 shortTitle: Configure code scanning
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
@@ -89,7 +89,7 @@ If you scan pull requests, then the results appear as alerts in a pull request c
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ### Defining the severities causing pull request check failure
 
-By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)."
+By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -351,7 +351,7 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 
 You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 {% if codeql-packs %}
 ### Working with custom configuration files
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 42c5f3df55..6dc4d24289 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -26,7 +26,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 622a6eb37f..6c1d00f0ab 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -16,6 +16,7 @@ topics:
   - Code scanning
 children:
   - /about-code-scanning
+  - /about-code-scanning-alerts
   - /triaging-code-scanning-alerts-in-pull-requests
   - /setting-up-code-scanning-for-a-repository
   - /managing-code-scanning-alerts-for-your-repository
@@ -28,4 +29,4 @@ children:
   - /running-codeql-code-scanning-in-a-container
   - /viewing-code-scanning-logs
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index bc07386975..7747b61120 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -23,62 +23,9 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
-## About alerts from {% data variables.product.prodname_code_scanning %}
-
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
-
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-
-{% data reusables.code-scanning.upload-sarif-alert-limit %}
-
-## About alerts details
-
-Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
-
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
-
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
-
-When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
-
-### About severity levels
-
-Alert severity levels may be `Error`, `Warning`, or `Note`.
-
-By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### About security severity levels
-
-{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
-
-To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
-
-By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-### About labels for alerts that are not found in application code
-
-{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
-
-- **Generated**: Code generated by the build process
-- **Test**: Test code
-- **Library**: Library or third-party code
-- **Documentation**: Documentation
-
-{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
-
-Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code.
-
-![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
-
-On the alert page, you can see that the filepath is marked as library code (`Library` label).
-
-![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
-
 ## Viewing the alerts for a repository
 
 Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
@@ -104,6 +51,8 @@ By default, the code scanning alerts page is filtered to show alerts for the def
 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
    ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
 
+For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
+
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
 
@@ -133,7 +82,7 @@ If you enter multiple filters, the view will show alerts matching _all_ these fi
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 
-You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
+You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
 
 {% endif %}
 
@@ -177,7 +126,7 @@ You can search the list of alerts. This is useful if there is a large number of
 
 {% endif %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index 9030845e11..d1fa89e9bb 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -23,7 +23,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index 57e621ed64..ef4ffcfa65 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -5,9 +5,7 @@ intro: You can add code scanning alerts to issues using task lists. This makes i
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
-  fpt: '*'
-  ghes: '> 3.3'
-  ghae: issue-5036
+  feature: code-scanning-task-lists
 type: how_to
 topics:
   - Advanced Security
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 8b4a6464af..66ae7d484f 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -21,7 +21,7 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index b60240da58..8271607e10 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -27,7 +27,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
@@ -191,6 +190,19 @@ For languages like Go, JavaScript, Python, and TypeScript, that {% data variable
 
 それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 詳しい情報については、「[イベント](/actions/learn-github-actions/introduction-to-github-actions#events)」を参照してください。
 
+### Check which query suites the workflow runs
+
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
+
+You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)」を参照してください。
+
+{% if codeql-ml-queries %}
+{% note %}
+
+**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+{% endnote %}
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ## 分析プラットフォーム間で異なる結果
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/index.md b/translations/ja-JP/content/code-security/code-scanning/index.md
index b65d41b2cd..915ff6aff7 100644
--- a/translations/ja-JP/content/code-security/code-scanning/index.md
+++ b/translations/ja-JP/content/code-security/code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /using-codeql-code-scanning-with-your-existing-ci-system
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
index 0a120a5059..d1f394b381 100644
--- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -19,7 +19,7 @@ topics:
   - Webhooks
   - Integration
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/index.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/index.md
index 4766d3072a..1e12c44022 100644
--- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/index.md
+++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /sarif-support-for-code-scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index ab3879863f..c1fc8e6166 100644
--- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -21,7 +21,7 @@ topics:
   - Integration
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index c0b9b3afea..0beaf40ec0 100644
--- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -24,7 +24,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index fba109bb62..0ecb4a0c59 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -166,7 +166,7 @@ codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
 | Option | Required | Usage |
 |--------|:--------:|-----|
 | `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. |
-| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/qlpacks/codeql/<language>-queries/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
 | <nobr>`--format`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
 | <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 | <nobr>`--sarif-category`<nobr> | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index 7c42e31833..6105ca77b6 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -28,7 +28,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
@@ -83,7 +83,7 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index 43e4875ffc..5c27c96939 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -28,4 +28,3 @@ children:
   - /migrating-from-the-codeql-runner-to-codeql-cli
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index 6541821e6f..47c336b8b1 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -50,7 +50,7 @@ These examples assume that the source code has been checked out to the current w
 
 These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH.
 
-In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable.
+In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via `stdin`, or is stored in the `$GITHUB_TOKEN` environment variable.
 
 The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code.
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index 441e52b87a..74078a9855 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -25,7 +25,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
index 50f9573aff..b2985b6bb9 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -24,7 +24,6 @@ topics:
   - CI
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md
index 92361d61a2..25412c70df 100644
--- a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md
@@ -139,3 +139,9 @@ You can view and manage alerts from security features to address dependencies an
 
 {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
+
+{% ifversion ghec %}
+## Further reading
+
+"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/code-security/guides.md b/translations/ja-JP/content/code-security/guides.md
index 946e5c5249..ecaf5f42ab 100644
--- a/translations/ja-JP/content/code-security/guides.md
+++ b/translations/ja-JP/content/code-security/guides.md
@@ -30,6 +30,7 @@ includeGuides:
   - /code-security/secret-scanning/secret-scanning-partners
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
diff --git a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
index 202d10637b..815bac14eb 100644
--- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
@@ -15,6 +15,8 @@ topics:
   - Security overview
   - Advanced Security
   - Alerts
+  - Dependabot
+  - Dependencies
   - Organizations
   - Teams
 shortTitle: About security overview
@@ -26,7 +28,7 @@ shortTitle: About security overview
 
 セキュリティの概要は、Organizationのセキュリティの状況の高レベルでの表示、あるいは介入が必要な問題のあるリポジトリを特定するために利用できます。
 
-- Organizationのレベルでは、セキュリティの概要はOrganizationが所有するリポジトリに関する集約されたリポジトリ固有のセキュリティ情報を表示します。
+- Organizationのレベルでは、セキュリティの概要はOrganizationが所有するリポジトリに関する集約されたリポジトリ固有のセキュリティ情報を表示します。 You can also filter information per security feature.
 - Teamレベルでは、セキュリティの概要はTeamが管理権限を持つリポジトリの固有のセキュリティ情報を表示します。 For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 - At the repository-level, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features not currently in use.
 
@@ -40,7 +42,7 @@ The application security team at your company can use the security overview for
 
 セキュリティの概要では、Organizationや特定のリポジトリ内のセキュリティリスクを理解するために、アラートを表示、ソート、フィルタリングできます。 The security summary is highly interactive, allowing you to investigate specific categories of information, based on qualifiers like alert risk level, alert type, and feature enablement. You can also apply multiple filters to focus on narrower areas of interest. たとえば、多数の{% data variables.product.prodname_dependabot_alerts %}が生じているプライベートリポジトリや、{% data variables.product.prodname_code_scanning %}アラートのないリポジトリを識別できます。 For more information, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
 
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
 
 In the security overview, at both the organization and repository level, there are dedicated views for specific security features, such as secret scanning alerts and code scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository.
 
diff --git a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
index 6d9c969dde..851f8deaf9 100644
--- a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
+++ b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   fpt: '*'
+  ghae: issue-4554
   ghes: '>3.1'
   ghec: '*'
 type: how_to
@@ -99,7 +100,7 @@ Available in the organization-level overview.
 | ------------------------- | ------------------------------ |
 | <code>topic:<em>TOPIC-NAME</em></code> | *TOPIC-NAME*で分類されるリポジトリを表示します。 |
 
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
 
 ## Filter by severity
 
@@ -121,16 +122,16 @@ Available in the code scanning alert views. All code scanning alerts have one of
 
 Available in the secret scanning alert views.
 
-| 修飾子                                                                                                                                                                                        | 説明                                                                                                                                                                                                                 |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `secret-type:SERVICE_PROVIDER`                                                                                                                                                             | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners) |
-| `secret-type:CUSTOM-PATTERN`                                                                                                                                                               | Displays alerts for secrets matching the specified custom pattern.                                                                                                                                                 |
-| {% ifversion not fpt %}For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."{% endif %} |                                                                                                                                                                                                                    |
+| 修飾子                                                                                                                                                                                        | 説明                                                                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret-type:SERVICE_PROVIDER`                                                                                                                                                             | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners)." |
+| `secret-type:CUSTOM-PATTERN`                                                                                                                                                               | Displays alerts for secrets matching the specified custom pattern.                                                                                                                                                   |
+| {% ifversion not fpt %}For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."{% endif %} |                                                                                                                                                                                                                      |
 
 ## Filter by provider
 
 Available in the secret scanning alert views.
 
-| 修飾子                      | 説明                                                                                                                                                                                                                            |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners) |
+| 修飾子                      | 説明                                                                                                                                                                                                                              |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners)." |
diff --git a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md
index 2cb29c6cdf..889db6dc48 100644
--- a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md
+++ b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   fpt: '*'
+  ghae: issue-5503
   ghes: '>3.1'
   ghec: '*'
 type: how_to
@@ -25,8 +26,8 @@ shortTitle: View the security overview
 {% data reusables.organizations.security-overview %}
 1. アラートの種類に対する集約された情報を見るには、**Show more（さらに表示）**をクリックしてください。 ![さらに表示ボタン](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
-
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
+1. Alternatively and optionally, use the sidebar on the left to filter information per security feature. On each page, you can use filters that are specific to each feature to fine-tune your search. ![Screenshot of the code scanning-specific page](/assets/images/help/organizations/security-overview-code-scanning-alerts.png)
 
 ## Viewing alerts across your organization
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index aeb4f66905..b1e0314a22 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -16,7 +16,7 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Use Dependabot with actions
+shortTitle: Use Dependabot with Actions
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
index cf937b43e3..0a38bb5acc 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
@@ -27,7 +27,9 @@ shortTitle: 設定オプション
 
 {% data variables.product.prodname_dependabot %} の設定ファイルである *dependabot.yml* では YAML 構文を使用します。 YAMLについて詳しくなく、学んでいきたい場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。
 
-このファイルは、リポジトリの `.github` ディレクトリに保存する必要があります。 *dependabot.yml* ファイルを追加または更新すると、即座にバージョン更新を確認します。 セキュリティアップデートに影響するオプションは、次にセキュリティアラートがセキュリティアップデートのためのプルリクエストをトリガーするときにも使用されます。 For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+このファイルは、リポジトリの `.github` ディレクトリに保存する必要があります。 *dependabot.yml* ファイルを追加または更新すると、即座にバージョン更新を確認します。 For more information and an example, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)."
+
+セキュリティアップデートに影響するオプションは、次にセキュリティアラートがセキュリティアップデートのためのプルリクエストをトリガーするときにも使用されます。  For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
 
 *dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 必要に応じて、最上位に `registries` キーを含めることができます。 ファイルは、`version: 2` で始まる必要があります。
 
@@ -75,7 +77,7 @@ shortTitle: 設定オプション
 
 脆弱性のあるパッケージマニフェストのセキュリティアップデートは、デフォルトブランチでのみ発生します。 設定オプションが同じブランチに設定され（`target-branch` を使用しない場合は true）、脆弱性のあるマニフェストの `package-ecosystem` と `directory` を指定している場合、セキュリティアップデートのプルリクエストで関連オプションが使用されます。
 
-一般に、セキュリティアップデートでは、メタデータの追加や動作の変更など、プルリクエストに影響する設定オプションが使用されます。 For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+一般に、セキュリティアップデートでは、メタデータの追加や動作の変更など、プルリクエストに影響する設定オプションが使用されます。 セキュリティアップデートに関する詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)」を参照してください。
 
 {% endnote %}
 
@@ -168,7 +170,7 @@ updates:
 
 {% note %}
 
-**注釈**: `schedule` は、{% data variables.product.prodname_dependabot %} が新規更新を試行するタイミングを設定します。 ただし、プルリクエストを受け取るタイミングはこれだけではありません。 更新は、 `dependabot.yml` ファイルへの変更、更新失敗後のマニフェストファイルへの変更、または {% data variables.product.prodname_dependabot_security_updates %} に基づいてトリガーされることがあります。 For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+**注釈**: `schedule` は、{% data variables.product.prodname_dependabot %} が新規更新を試行するタイミングを設定します。 ただし、プルリクエストを受け取るタイミングはこれだけではありません。 更新は、 `dependabot.yml` ファイルへの変更、更新失敗後のマニフェストファイルへの変更、または {% data variables.product.prodname_dependabot_security_updates %} に基づいてトリガーされることがあります。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} プルリクエストの頻度](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)」および「[{% data variables.product.prodname_dependabot_security_updates %} について](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)」を参照してください。
 
 {% endnote %}
 
@@ -305,7 +307,7 @@ updates:
 
 リポジトリが`ignore`の設定を保存したかは、リポジトリで`"@dependabot ignore" in:comments`を検索すれば調べられます。 この方法で無視された依存関係の無視を解除したいなら、Pull Requestを再度オープンしてください。
 
-For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+`@dependabot ignore` コマンドに関する詳細については、「[依存関係の更新に関するプルリクエストを管理する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)」をご覧ください。
 
 #### 無視する依存関係とバージョンを指定する
 
@@ -488,9 +490,9 @@ updates:
 
 ### `registries`
 
-バージョン更新の実行時に {% data variables.product.prodname_dependabot %} がプライベートパッケージレジストリにアクセスできるようにするには、関係する `updates` 設定に `registries` 設定を含める必要があります。 `registries` を `"*"` に設定することで、定義されたリポジトリをすべて使用できるようにすることができます。 また、更新が使用できるレジストリをリストすることもできます。 これを行うには、_dependabot.yml_ ファイルの最上位の `registries` セクションで定義されているレジストリの名前を使用します。
+バージョン更新の実行時に {% data variables.product.prodname_dependabot %} がプライベートパッケージレジストリにアクセスできるようにするには、関係する `updates` 設定に `registries` 設定を含める必要があります。 `registries` を `"*"` に設定することで、定義されたリポジトリをすべて使用できるようにすることができます。 また、更新が使用できるレジストリをリストすることもできます。 これを行うには、_dependabot.yml_ ファイルの最上位の `registries` セクションで定義されているレジストリの名前を使用します。 For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below.
 
-{% data variables.product.prodname_dependabot %} が `bundler`、`mix`、および `pip` パッケージマネージャーを使用してプライベートレジストリの依存関係を更新できるようにするため、外部コードの実行を許可できます。 詳しい情報については、[`insecure-external-code-execution`](#insecure-external-code-execution) を参照してください。
+{% data variables.product.prodname_dependabot %} が `bundler`、`mix`、および `pip` パッケージマネージャーを使用してプライベートレジストリの依存関係を更新できるようにするため、外部コードの実行を許可できます。 For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
 
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
index a63ca2bd83..8439c9df42 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -51,4 +51,4 @@ If you are using private repositories, you will have to grant Dependabot access
 
 If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
 
-If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
+If you have any questions or need help migrating, you can view or open issues in the [`dependabot/dependabot-core`](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 4cc8e5b8c8..87bb27fc10 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -38,7 +38,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
 
 時に、マニフェスト内の 1 つの依存関係のバージョンを更新して、プルリクエストを生成することがあります。 ただし、この直接依存関係の更新バージョンでも依存関係が更新されている場合は、プルリクエストに予想よりも多くの変更が加えられている可能性があります。 各マニフェストとロックファイルの依存関係のレビューにより、何が変更されたか、新しい依存関係バージョンのいずれかに既知の脆弱性が含まれているかどうかを簡単に確認できます。
 
-プルリクエストで依存関係のレビューを確認し、脆弱性としてフラグが付けられている依存関係を変更することで、プロジェクトに脆弱性が追加されるのを防ぐことができます。 依存関係のレビューの動作に関する詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」を参照してください。
+プルリクエストで依存関係のレビューを確認し、脆弱性としてフラグが付けられている依存関係を変更することで、プロジェクトに脆弱性が追加されるのを防ぐことができます。 For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
 
 {% data variables.product.prodname_dependabot_alerts %} は、すでに依存関係にある脆弱性を検出しますが、あとで修正するよりも、潜在的な問題が持ち込まれることを回避する方がはるかに良いです。 {% data variables.product.prodname_dependabot_alerts %} に関する詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)」を参照してください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 716a544e20..9dfc90486b 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -77,6 +77,9 @@ The recommended formats explicitly define which versions are used for all direct
 | --- | --- | --- | ---|
 | Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
 | `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+{%- if github-actions-in-dependency-graph %}
+| {% data variables.product.prodname_actions %} workflows<sup>[1]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
+{%- endif %}
 {%- ifversion fpt or ghes > 3.2 or ghae %}
 | Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
 {%- elsif ghes = 3.2 %}
@@ -84,18 +87,28 @@ The recommended formats explicitly define which versions are used for all direct
 {%- endif %}
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
-| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* |
+| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
 {%- ifversion fpt or ghes > 3.3 %}
 | Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
+{% if github-actions-in-dependency-graph %}
+[1] Please note that {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)."
+
+[2] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+
+{% else %}
+[1] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+{% endif %}
+
+{% if github-actions-in-dependency-graph %}
 {% note %}
 
-**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+**Note:** {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.
 
 {% endnote %}
-
+{% endif %}
 ## Further reading
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 7c6284a790..5b3bb39b73 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -12,7 +12,7 @@ shortTitle: プライベートイメージレジストリ
 
 ## About private image registries and {% data variables.product.prodname_codespaces %}
 
-A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more devcontainers. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
+A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more images. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
 
 {% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry.
 
@@ -87,7 +87,7 @@ To access AWS Elastic Container Registry (ECR),  you can provide an AWS access k
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
 *_CONTAINER_REGISTRY_USER = <AWS_ACCESS_KEY_ID>
-*_container_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
+*_CONTAINER_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
 ```
 
 You must also ensure you have the appropriate AWS IAM permissions to perform the credential swap (e.g. `sts:GetServiceBearerToken`) as well as the ECR read operation (either `AmazonEC2ContainerRegistryFullAccess` or `ReadOnlyAccess`).
@@ -97,7 +97,7 @@ Alternatively, if you don't want GitHub to perform the credential swap on your b
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
 *_CONTAINER_REGISTRY_USER = AWS
-*_container_REGISTRY_PASSWORD = <TOKEN>
+*_CONTAINER_REGISTRY_PASSWORD = <TOKEN>
 ```
 
 Since these tokens are short lived and need to be refreshed periodically, we recommend providing an access key ID and secret.
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index e5d92db636..78db108ae7 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -19,7 +19,7 @@ To learn about pricing for {% data variables.product.prodname_codespaces %}, see
 
 {% data reusables.codespaces.codespaces-billing %}
 
-- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
+- As an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
 
 - For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 749ae06a6c..cb358f2cbf 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -41,12 +41,11 @@ Organization リポジトリのシークレットを作成するには、管理
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. ページを下にスクロールし、[**Secrets**] で [**Codespaces**] を選択します。 ![サイドバーの Codespaces オプション](/assets/images/help/codespaces/codespaces-option-secrets.png)
-1. ページの上部にある [**New repository secret**] をクリックします。
-1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
-1. シークレットの値を入力します。
-1. [**Add secret（シークレットの追加）**] をクリックします。
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+2. ページの上部にある [**New repository secret**] をクリックします。
+3. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+4. シークレットの値を入力します。
+5. [**Add secret（シークレットの追加）**] をクリックします。
 
 ## Organization にシークレットを追加する
 
@@ -56,13 +55,12 @@ Organizationでシークレットを作成する場合、ポリシーを使用
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. ページを下にスクロールし、[**Secrets**] で [**Codespaces**] を選択します。 ![サイドバーの Codespaces オプション](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
-1. ページの上部にある [**New organization secret**] をクリックします。
-1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
-1. シークレットの **Value（値）** を入力します。
-1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 ![プライベートリポジトリが選択された [Repository Access] リスト](/assets/images/help/codespaces/secret-repository-access.png)
-1. [**Add secret（シークレットの追加）**] をクリックします。
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+2. ページの上部にある [**New organization secret**] をクリックします。
+3. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+4. シークレットの **Value（値）** を入力します。
+5. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 ![プライベートリポジトリが選択された [Repository Access] リスト](/assets/images/help/codespaces/secret-repository-access.png)
+6. [**Add secret（シークレットの追加）**] をクリックします。
 
 ## Organizationレベルのシークレットへのアクセスの確認
 
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index fbb2e9d8e7..ceb58ad1de 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -47,34 +47,30 @@ If you add an organization-wide policy, you should set it to the largest choice
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.click-codespaces %}
-1. Under "Codespaces", click **Policy**.
-
-   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
-
-1. On the "Codespace policies" page, click **Create Policy**.
-1. Enter a name for your new policy.
-1. Click **Add constraint** and choose **Machine types**.
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policy**.
+2. On the "Codespace policies" page, click **Create Policy**.
+3. Enter a name for your new policy.
+4. Click **Add constraint** and choose **Machine types**.
 
    ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
 
-1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+5. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
 
    ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
 
-1. In the "Change policy target" area, click the dropdown button.
-1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
-1. [**Selected repositories**] を選択した場合、以下の手順に従います。
+6. In the "Change policy target" area, click the dropdown button.
+7. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+8. [**Selected repositories**] を選択した場合、以下の手順に従います。
    1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。
 
       ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
 
-   1. Select the repositories you want this policy to apply to.
-   1. At the bottom of the repository list, click **Select repositories**.
+   2. Select the repositories you want this policy to apply to.
+   3. At the bottom of the repository list, click **Select repositories**.
 
       ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
 
-1. [**Save**] をクリックします。
+9. [**Save**] をクリックします。
 
 ## Editing a policy
 
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
index 53a049097b..f3e81596c9 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -33,7 +33,7 @@ hidden: true
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 デフォルト設定では、codespace のコンテナには、Java、nvm、npm、yarn を含む多くの言語とランタイムがあります。 また、git、wget、rsync、openssh、nano などの一般的なツールセットも含まれています。
+codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and Yarn. また、git、wget、rsync、openssh、nano などの一般的なツールセットも含まれています。
 
 vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
diff --git a/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
index e7d06b6fac..31b86e449d 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
@@ -26,7 +26,7 @@ The name the codespace is also included in many of the log files. For example, i
 
 ### Codespaces IDs
 
-Every codespace also has an ID (identifer). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID.
+Every codespace also has an ID (identifier). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID.
 
 1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace.
 2. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID.
diff --git a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index 4e34aa14a9..6550c52228 100644
--- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -33,7 +33,7 @@ Organization からユーザのブロックを解除すると、そのユーザ
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.moderation-settings %}
+{% data reusables.organizations.moderation-settings %}, then click **Blocked users**.
 5. [Blocked users] の下で、ブロックを解除したいユーザの横にある [**Unblock**] をクリックします。 ![ユーザブロックの解除ボタン](/assets/images/help/organizations/org-unblock-user-button.png)
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index 7fa5d4854a..2a082c3f0e 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,6 +27,6 @@ shortTitle: アカウントのインタラクションの制限
 ## ユーザアカウントの操作を制限する
 
 {% data reusables.user_settings.access_settings %}
-1. [User settings] サイドバーの [Moderation settings] で、[**Interaction limits**] をクリックします。 ![[User settings] サイドバーの [Interaction limits] タブ](/assets/images/help/settings/settings-sidebar-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![[Temporary interaction limits] のオプション](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index d5eab97571..0259923a3d 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -33,8 +33,7 @@ Organization のオーナーは、特定の期間だけユーザをブロック
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. [organization settings] サイトバーで、[**Moderation settings**] をクリックします。 ![[organization settings] サイトバーの [Moderation settings]](/assets/images/help/organizations/org-settings-moderation-settings.png)
-1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![[organization settings] サイトバーの [Interaction limits] タブ](/assets/images/help/organizations/org-settings-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![[Temporary interaction limits] のオプション](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index 509b82d4c5..577b43d0a9 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -28,8 +28,7 @@ shortTitle: リポジトリ内でのインタラクションの制限
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. 左サイドバーで [**Moderation settings**] をクリックします。 ![[Repository settings] サイトバーの [Moderation settings]](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![リポジトリの設定での [Interaction limits] ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![[Temporary interaction limits] のオプション](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
new file mode 100644
index 0000000000..8fadf02ae8
--- /dev/null
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
@@ -0,0 +1,641 @@
+---
+title: Common validation errors when creating issue forms
+intro: 'You may see some of these common validation errors when creating, saving, or viewing issue forms.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+---
+
+<!--UI-LINK: We link to individual anchors within this file from the issue template editor when the given YAML error is thrown. Links to and anchors within this file should be preserved or should be updated in github/github if they are changed -->
+{% data reusables.community.issue-forms-beta %}
+
+## Required top level key `name` is missing
+
+The template does not contain a `name` field, which means it is not clear what to call your issue template when giving users a list of options.
+
+### サンプル
+
+```yaml
+description: "Thank you for reporting a bug!"
+...
+```
+
+The error can be fixed by adding `name` as a key.
+
+```yaml
+name: "Bug report"
+description: "Thank you for reporting a bug!"
+...
+```
+
+## `key` must be a string
+
+This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported.
+
+### サンプル
+
+The `description` below is being parsed as a Boolean, but it should be a string.
+
+```yaml
+name: "Bug report"
+description: true
+...
+```
+
+The error can be fixed by providing a string as the value. Strings may need to be wrapped in double quotes to be successfully parsed. For example, strings that contain `'` must be wrapped in double quotes.
+
+```yaml
+name: "Bug report"
+description: "true"
+...
+```
+
+Empty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string.
+
+```yaml
+name: ""
+description: "File a bug report"
+assignees: "      "
+...
+```
+
+The error can be fixed by correcting the value to be a non-empty string. If the field is not required, you should delete the key-value pair.
+
+```yaml
+name: "Bug Report"
+description: "File a bug report"
+...
+```
+
+## `input` is not a permitted key
+
+An unexpected key was supplied at the top level of the template. For more information about which top-level keys are supported, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax)."
+
+### サンプル
+
+```yaml
+name: "Bug report"
+hello: world
+...
+```
+
+The error can be fixed by removing the unexpected keys.
+
+```yaml
+name: "Bug report"
+...
+```
+
+## Forbidden keys
+
+YAML parses certain strings as `Boolean` values. To avoid this, we have explicitly forbidden the usage of the following keys:
+
+`y`, `Y`, `yes`, `Yes`, `YES`, `n`, `N`, `no`, `No`, `NO`, `true`, `True`, `TRUE`, `false`, `False`, `FALSE`, `on`, `On`, `ON`, `off`, `Off`, `OFF`
+
+The error can be fixed by removing the forbidden keys.
+
+## Body must contain at least one non-markdown field
+
+Issue forms must accept user input, which means that at least one of its fields must contain a user input field. A `markdown` element is static text, so a `body` array cannot contain only `markdown` elements.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+```
+
+The error can be fixed by adding non-markdown elements that accept user input.
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+- type: textarea
+  attributes:
+    label: "What's wrong?"
+```
+
+## Body must have unique ids
+
+If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: name
+  attributes:
+    label: Last name
+```
+
+The error can be fixed by changing the `id` for one of these inputs, so that every `input` field has a unique `id` attribute.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: surname
+  attributes:
+    label: Last name
+```
+
+## Body must have unique labels
+
+When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Name
+```
+
+The error can be fixed by changing the `label` attribute for one of the input fields to ensure that each `label` is unique.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Operating System
+```
+
+Input fields can also be differentiated by their `id` attribute. If duplicate `label` attributes are required, you can supply at least one `id` to differentiate two elements with identical labels.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: textarea
+  id: name_2
+  attributes:
+    label: Name
+```
+
+`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+
+
+## Labels are too similar
+
+Similar labels may be processed into identical references. If an `id` attribute is not provided for an `input`, the `label` attribute is used to generate a reference to the `input` field. To do this, we process the `label` by leveraging the Rails [parameterize](https://apidock.com/rails/ActiveSupport/Inflector/parameterize) method. In some cases, two labels that are distinct can be processed into the same parameterized string.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: name
+  attributes:
+    label: Name???????
+```
+
+The error can be fixed by adding at least one differentiating alphanumeric character, `-`, or `_` to one of the clashing labels.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  attributes:
+    label: Your name
+```
+
+The error can also be fixed by giving one of the clashing labels a unique `id`.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: your-name
+  attributes:
+    label: Name???????
+```
+
+## Checkboxes must have unique labels
+
+When a `checkboxes` element is present, each of its nested labels must be unique among its peers, as well as among other input types.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+The error can be fixed by changing the `label` attribute for one of these inputs.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Your name
+```
+
+Alternatively, you can supply an `id` to any clashing top-level elements. Nested checkbox elements do not support the `id` attribute.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+
+## Body[i]: required key type is missing
+
+Each body block must contain the key `type`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the zero-indexed index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+The error can be fixed by adding the key `type` with a valid input type as the value. For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys)."
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+## Body[i]: `x` is not a valid input type
+
+One of the body blocks contains a type value that is not one of the [permitted types](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys).
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- type: x
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+The error can be fixed by changing `x` to one of the valid types.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+## Body[i]: required attribute key `value` is missing
+
+One of the required `value` attributes has not been provided. The error occurs when a block does not have an `attributes` key or does not have a `value` key under the `attributes` key.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+- type: markdown
+```
+
+The error in this example can be fixed by adding `value` as a key under `attributes` in the second list element of `body`.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+- type: markdown
+  attributes:
+    value: "This is working now!"
+```
+
+## Body[i]: label must be a string
+
+Within its `attributes` block, a value has the wrong data type.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+The `label` below is being parsed as a Boolean, but it should be a string.
+
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: true
+```
+
+The error can be fixed by supplying a string value for `label`. If you want to use a `label` value that may be parsed as a Boolean, integer, or decimal, you should wrap the value in quotes. For example, `"true"` or `"1.3"` instead of `true` or `1.3`.
+
+```yaml
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: Environment Details
+```
+
+Empty strings, or strings consisting of only whitespaces, are not permissible when an attribute expects a string. For example, `""` or `"     "` are not allowed.
+
+If the attribute is required, the value must be a non-empty string. If the field is not required, you should delete the key-value pair.
+
+```yaml
+body:
+- type: input
+  attributes:
+    label: "Name"
+```
+
+## Body[i]: `id` can only contain numbers, letters, -, _
+
+`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first name
+  attributes:
+    label: First name
+```
+
+The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first-name
+  attributes:
+    label: First name
+```
+
+## Body[i]: `x` is not a permitted key
+
+An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- type: markdown
+  x: woof
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+The error can be fixed by removing extra keys and only using `type`, `attributes`, and `id`.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+## Body[i]: `label` contains forbidden word
+
+To minimize the risk of private information and credentials being posted publicly in GitHub Issues, some words commonly used by attackers are not permitted in the `label` of input or textarea elements.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Password
+```
+
+The error can be fixed by removing terms like "password" from any `label` fields.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Username
+```
+
+## Body[i]: `x` is not a permitted attribute
+
+An invalid key has been supplied in an `attributes` block.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    x: "a random key!"
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+The error can be fixed by removing extra keys and only using permitted attributes.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+## Body[i]: `options` must be unique
+
+For checkboxes and dropdown input types, the choices defined in the `options` array must be unique.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - ice cream
+      - pie
+```
+
+The error can be fixed by ensuring that no duplicate choices exist in the `options` array.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - pie
+```
+
+## Body[i]: `options` must not include the reserved word, none
+
+"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+      - None
+  validations:
+    required: true
+```
+
+The error can be fixed by removing "None" as an option. If you want a contributor to be able to indicate that they like none of those types of pies, you can additionally remove the `required` validation.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+```
+
+In this example, "None" will be auto-populated as a selectable option.
+
+## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes
+
+There are a number of English words that become processed into Boolean values by the YAML parser unless they are wrapped in quotes. For dropdown `options`, all items must be strings rather than Booleans.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### サンプル
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - Yes
+      - No
+      - Maybe
+```
+
+The error can be fixed by wrapping each offending option in quotes, to prevent them from being processed as Boolean values.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - "Yes"
+      - "No"
+      - Maybe
+```
+
+## 参考リンク
+
+- [YAML](https://yaml.org/)
+- [Issue フォームの構文](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 7ea0760829..7597cda3a1 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -21,5 +21,6 @@ children:
   - /syntax-for-githubs-form-schema
   - /creating-a-pull-request-template-for-your-repository
   - /manually-creating-a-single-issue-template-for-your-repository
+  - /common-validation-errors-when-creating-issue-forms
 ---
 
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
index 5f5bd83b6b..34c002298f 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
@@ -241,7 +241,7 @@ body:
 
 | キー        | 説明                                                  | 必須 | 種類   | デフォルト                                           | 有効な値                                            |
 | --------- | --------------------------------------------------- | -- | ---- | ----------------------------------------------- | ----------------------------------------------- |
-| `ラベル`     | フォームに表示される、予想されるユーザ入力の簡単な説明。                        | 任意 | 文字列型 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `ラベル`     | フォームに表示される、予想されるユーザ入力の簡単な説明。                        | 必須 | 文字列型 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 | `説明`      | フォームに表示されるチェックボックスのセットの説明。 Markdown フォーマットをサポートします。 | 任意 | 文字列型 | 空の文字列                                           | {% octicon "dash" aria-label="The dash icon" %}
 | `options` | ユーザが選択できるチェックボックスの配列。 構文については、以下を参照してください。          | 必須 | 配列   | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index c8abd40621..ab801bd2a7 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -40,7 +40,7 @@ body:
 | `説明`        | A description for the issue form template, which appears in the template chooser interface. | 必須 | 文字列型                            |
 | `body`      | Definition of the input types in the form.                                                  | 必須 | 配列                              |
 | `assignees` | People who will be automatically assigned to issues created with this template.             | 任意 | Array or comma-delimited string |
-| `labels`    | Labels that will automatically be added to issues created with this template.               | 任意 | 文字列型                            |
+| `labels`    | Labels that will automatically be added to issues created with this template.               | 任意 | Array or comma-delimited string |
 | `title`     | A default title that will be pre-populated in the issue submission form.                    | 任意 | 文字列型                            |
 
 For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)."
@@ -165,3 +165,4 @@ body:
 ## 参考リンク
 
 - [YAML](https://yaml.org/)
+- [Common validation errors when creating issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms)
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 2555804385..e5f4ea099d 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -99,7 +99,7 @@ webhook を保護するためにシークレットが必要なアプリケーシ
 | [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | [Code scanning API](/rest/reference/code-scanning/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
 | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                  |
 | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                       | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                               |
-| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                       | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                  |
+| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                       | [Statuses API](/rest/reference/commits#commit-statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                         |
 | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 | `vulnerability_alerts`                                                                                                           | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に関するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)」を参照。 `none`、`read` のいずれかです。{% endif %}
 | `Watch`                                                                                                                          | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                                    |
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index ab0519c401..4c72f932c4 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -449,8 +449,8 @@ While most of your API インタラクションのほとんどは、サーバー
 {% ifversion fpt or ghec %}
 #### Organization Team Sync
 
-* [Teamのidpグループの一覧表示](/rest/reference/teams#list-idp-groups-for-a-team)
-* [idpグループの接続の作成あるいは更新](/rest/reference/teams#create-or-update-idp-group-connections)
+* [List IdP groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
+* [Create or update IdP group connections](/rest/reference/teams#create-or-update-idp-group-connections)
 * [OrganizationのIdpグループの一覧表示](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
index 034abd8ec8..913ba12786 100644
--- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -54,7 +54,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 ## ステップ 1. 新しいSmeeチャンネルの開始
 
-ローカルのマシンをインターネットに公開することなく、GitHubがwebhookを送信するのを支援するために、Smeeというツールが利用できます。 まず https://smee.io にアクセスして、**Start a new channel**をクリックしてください。 [ngrok](https://dashboard.ngrok.com/get-started)や[localtunnel](https://localtunnel.github.io/www/)のような、ローカルマシンをインターネットに公開してくれる他のツールに慣れているなら、それらを使ってもかまいません。
+ローカルのマシンをインターネットに公開することなく、GitHubがwebhookを送信するのを支援するために、Smeeというツールが利用できます。 まず https://smee.io にアクセスして、**Start a new channel**をクリックしてください。 If you're already comfortable with other tools that expose your local machine to the internet like [`ngrok`](https://dashboard.ngrok.com/get-started) or [`localtunnel`](https://localtunnel.github.io/www/), feel free to use those.
 
 ![Smeeの新規チャンネルボタン](/assets/images/smee-new-channel.png)
 
@@ -91,7 +91,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 `smee --url <unique_channel>`というコマンドは、Smeeに対してSmeeのチャンネルが受信したすべてのwebhookイベントを、コンピューター上で動作するSmeeクライアントに転送するように指示しています。 `--path /event_handler`オプションは、イベントを`/event_handler`というルートに転送します。このルートについては[後のセクション](#step-5-review-the-github-app-template-code)で取り上げます。 `--port 3000`オプションはポート3000を指定しており、サーバーはこのポートで待ち受けます。 Smeeを使えば、GitHubからのwebhookを受信するためにあなたのマシンがパブリックなインターネットに対してオープンである必要はありません。 また、ブラウザでSmeeのURLを開いて、受信したwebhookのペイロードを調べることもできます。
 
-このターミナルのウィンドウは開いたままにしておき、このガイドの残りのステップを完了させるまでの間、Smeeに接続したままにしておくことをおすすめします。 ユニークなドメインを失うことなくSmeeのクライアントの接続を切って、接続しなおすことも_できます_が（ngrokとは違って）、これは接続したままにしておいて、別のターミナルウィンドウで他のコマンドラインのタスクを行うようにするほうが簡単でしょう。
+このターミナルのウィンドウは開いたままにしておき、このガイドの残りのステップを完了させるまでの間、Smeeに接続したままにしておくことをおすすめします。 Although you _can_ disconnect and reconnect the Smee client without losing your unique domain (unlike `ngrok`), you may find it easier to leave it connected and do other command-line tasks in a different Terminal window.
 
 ## ステップ 2. 新しいGitHub Appの登録
 
@@ -131,7 +131,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 アプリケーションを作成すると、[アプリケーションの設定ページ](https://github.com/settings/apps)に戻されます。 ここで行うことがあと2つあります。
 
-* **アプリケーションの秘密鍵の生成。**これは後でアプリケーションを認証するために必要です。 ページをスクロールダウンして、**Generate a private key（秘密鍵の生成）**をクリックしてください。 生成されたPEMファイル（_`app-name`_-_`date`_-private-key.pemというような名前）を、また見つけられるディレクトリに保存してください。
+* **アプリケーションの秘密鍵の生成。**これは後でアプリケーションを認証するために必要です。 ページをスクロールダウンして、**Generate a private key（秘密鍵の生成）**をクリックしてください。 Save the resulting `PEM` file (called something like  _`app-name`_-_`date`_-`private-key.pem`) in a directory where you can find it again.
 
     ![秘密鍵の生成ダイアログ](/assets/images/private_key.png)
 
diff --git a/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
index c6e16f8c09..02485f68ee 100644
--- a/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
+++ b/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
@@ -157,7 +157,7 @@ end
 
 このコードは[create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run)メソッドを使用して、[Create a check run](/rest/reference/checks#create-a-check-run)エンドポイントを呼び出します。
 
-チェック実行を作成するために必要なのは、`name` と `head_sha` の 2 つの入力パラメータのみです。 このクイックスタートでは、後で [Rubocop](https://rubocop.readthedocs.io/en/latest/) を使用して CI テストを実装します。そのため、ここでは「Octo Rubocop」という名前を使っていますが、チェック実行には任意の名前を選ぶことができます。
+チェック実行を作成するために必要なのは、`name` と `head_sha` の 2 つの入力パラメータのみです。 We will use [RuboCop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo RuboCop" is used here, but you can choose any name you'd like for the check run.
 
 ここでは基本的な機能を実行するため必要なパラメータのみを指定していますが、チェック実行について必要な情報を収集するため、後でチェック実行を更新することになります。 デフォルトでは、GitHub は `status` を `queued` に設定します。
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index bef496e681..73c0806579 100644
--- a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -29,7 +29,7 @@ Insightsページには、選択された期間に対する以下のパフォー
 
 * **Subscription value:** サブスクリプションで可能な合計収入（米ドル）。 この値は、プランや無料トライアルがまったくキャンセルされず、すべてのクレジット取引が成功した場合に可能な収入を示します。 subscription valueには、選択された期間内に無料トライアルで始まったプランの全額が、仮にその期間に金銭取引がなかったとしても含まれます。 subscription valueには、選択された期間内にアップグレードされたプランの全額も含まれますが、日割り計算の文は含まれません。 個別の取引を見てダウンロードするには、「[GitHub Marketplaceの取引](/marketplace/github-marketplace-transactions/)」を参照してください。
 * **Visitors:** GitHub Appのリスト内のページを見た人数。 この数字には、ログインした訪問者とログアウトした訪問者がどちらも含まれます。
-* **Pageviews:** GitHub Appのリスト内のページが受けた閲覧数です。 一人の訪問者が複数のページビューを生成できます。
+* **Pageviews:** GitHub Appのリスト内のページが受けた閲覧数です。 A single visitor can generate more than one page view.
 
 {% note %}
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
index a81fffd57b..fcb58ca8d3 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
@@ -19,7 +19,7 @@ shortTitle: リストのサブミット
 
   ![Marketplaceのリストのドラフトの概要オプション](/assets/images/marketplace/edit-marketplace-listing-overview.png)
 
-2. [**Request publish**] をクリックして、完成したアプリケーションのリストをサブミットします。
+2. To submit your completed app listing, click **Request publish**.
 
   ![下に提出ボタンの付いた、[Publish your app to Marketplace] チェックリスト](/assets/images/marketplace/publish-your-app-checklist-and-submission.png)
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
index 54fb39ac9f..afde8edef1 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
@@ -58,7 +58,7 @@ When a customer purchases your app, you must send the customer through the OAuth
 
 * If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)."
 
-For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize.
+For either type of app, the first step is to redirect the customer to [https://github.com/login/oauth/authorize](https://github.com/login/oauth/authorize).
 
 After the customer completes the authorization, your app receives an OAuth access token for the customer. You'll need this token for the next step.
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index deefb7ad2b..493ff4f046 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -50,7 +50,7 @@ GitHubは、変更が有効になるとwebhookを送信します。 たとえば
 
 アップグレードURLを使い、ユーザをアプリケーションのUIからGitHub上でのアップグレードへリダイレクトできます。
 
-```
+```text
 https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
 ```
 
diff --git a/translations/ja-JP/content/developers/overview/about-githubs-apis.md b/translations/ja-JP/content/developers/overview/about-githubs-apis.md
index 2db72b60e3..ac464ccfc7 100644
--- a/translations/ja-JP/content/developers/overview/about-githubs-apis.md
+++ b/translations/ja-JP/content/developers/overview/about-githubs-apis.md
@@ -3,6 +3,8 @@ title: GitHub APIについて
 intro: '{% data variables.product.prodname_dotcom %}の体験を拡張し、カスタマイズするために、{% data variables.product.prodname_dotcom %}のAPIについて学んでください。'
 redirect_from:
   - /v3/versions
+  - /articles/getting-started-with-the-api
+  - /github/extending-github/getting-started-with-the-api
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
index 1d716adaf7..d54721774e 100644
--- a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
+++ b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
@@ -34,11 +34,11 @@ SSHエージェントのフォワーディング、OAuthトークンでのHTTPS
 #### セットアップ
 
 1. エージェントのフォワーディングをローカルでオンにしてください。 詳しい情報については[SSHエージェントフォワーディングのガイド][ssh-agent-forwarding]を参照してください。
-2. エージェントフォワーディングを使用するように、デプロイスクリプトを設定してください。 たとえばbashのスクリプトでは、以下のようにしてエージェントのフォワーディングを有効化することになるでしょう。 `ssh -A serverA 'bash -s' < deploy.sh`
+2. エージェントフォワーディングを使用するように、デプロイスクリプトを設定してください。 For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh`
 
 ## OAuthトークンを使ったHTTPSでのクローニング
 
-SSHキーを使いたくないなら、[OAuthトークンでHTTPS][git-automation]を利用できます。
+If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
 
 #### 長所
 
@@ -57,7 +57,7 @@ SSHキーを使いたくないなら、[OAuthトークンでHTTPS][git-automatio
 
 #### セットアップ
 
-[トークンでのGit自動化ガイド][git-automation]を参照してください。
+See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
 ## デプロイキー
 
@@ -78,7 +78,7 @@ SSHキーを使いたくないなら、[OAuthトークンでHTTPS][git-automatio
 
 #### セットアップ
 
-1. サーバー上で[`ssh-keygen`の手順を実行][generating-ssh-keys]し、生成された公開／秘密RSAキーのペアを保存した場所を覚えておいてください。
+1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair key pair.
 2. {% data variables.product.product_name %}の任意のページの右上で、プロフィールの写真をクリックし、続いて**Your profile（あなたのプロフィール）**をクリックしてください。 ![プロフィールへのアクセス](/assets/images/profile-page.png)
 3. プロフィールページで**Repositories（リポジトリ）**をクリックし、続いてリポジトリの名前をクリックしてください。 ![リポジトリのリンク](/assets/images/repos.png)
 4. リポジトリで**Settings（設定）**をクリックしてください。 ![リポジトリの設定](/assets/images/repo-settings.png)
@@ -182,10 +182,8 @@ GitHub Appは{% data variables.product.product_name %}でも主役級の存在
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
+[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
-[git-automation]: /articles/git-automation-with-oauth-tokens
-[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
-
diff --git a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
index ab90b0cb6b..241d7f2bcc 100644
--- a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
@@ -79,7 +79,7 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 
 ### コードをのチェックアウトにはSSH URLを使わなければならない
 
-SSH転送はHTTP(s) URLでは動作せず、SSH URLでのみ動作します。 サーバー上の*.git/config*ファイルを調べて、URLが以下のようなSSHスタイルのURLになっていることを確認してください。
+SSH転送はHTTP(s) URLでは動作せず、SSH URLでのみ動作します。 サーバー上の`.git/config`ファイルを調べて、URLが以下のようなSSHスタイルのURLになっていることを確認してください。
 
 ```shell
 [remote "origin"]
@@ -107,7 +107,7 @@ $ exit
 # Returns to your local command prompt
 ```
 
-上の例では、*~/.ssh/config*というファイルがまずロードされ、それから*/etc/ssh_config*が読まれます。  以下のコマンドを実行すれば、そのファイルが設定を上書きしているかを調べることができます。
+上の例では、`~/.ssh/config`というファイルがまずロードされ、それから`/etc/ssh_config`が読まれます。  以下のコマンドを実行すれば、そのファイルが設定を上書きしているかを調べることができます。
 
 ```shell
 $ cat /etc/ssh_config
@@ -117,7 +117,7 @@ $ cat /etc/ssh_config
 >   ForwardAgent no
 ```
 
-この例では、*/etc/ssh_config*ファイルが`ForwardAgent no`と具体的に指定しており、これはエージェント転送をブロックするやり方です。 この行をファイルから削除すれば、エージェント転送は改めて動作するようになります。
+この例では、`/etc/ssh_config`ファイルが`ForwardAgent no`と具体的に指定しており、これはエージェント転送をブロックするやり方です。 この行をファイルから削除すれば、エージェント転送は改めて動作するようになります。
 
 ### サーバーはインバウンド接続でSSHエージェント転送を許可していなければならない
 
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
index 5cd5d819fd..8abf7d6134 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
@@ -22,9 +22,9 @@ webhookの作成は、2ステップのプロセスです。 まず、webhookを{
 
 ## ローカルホストをインターネットに公開する
 
-このチュートリアルでは、{% data variables.product.prodname_dotcom %}からメッセージを受信するためにローカルサーバーを使用します。 そのためには、まずローカル開発環境をインターネットに公開する必要があります。 そのためにngrokを使用しましょう。 ngrokは無料で、主要なオペレーティングシステムで利用できます。 詳しい情報については、[ngrokのダウンロードページ](https://ngrok.com/download)を参照してください。
+このチュートリアルでは、{% data variables.product.prodname_dotcom %}からメッセージを受信するためにローカルサーバーを使用します。 そのためには、まずローカル開発環境をインターネットに公開する必要があります。 そのためにngrokを使用しましょう。 ngrokは無料で、主要なオペレーティングシステムで利用できます。 For more information, see [the `ngrok` download page](https://ngrok.com/download).
 
-ngrokをインストールしたら、コマンドラインで `./ngrok http 4567` を実行してローカルホストを公開できます。 4567は、サーバーがメッセージを受信するポート番号です。 以下のような行が表示されるはずです。
+After installing `ngrok`, you can expose your localhost by running `./ngrok http 4567` on the command line. 4567は、サーバーがメッセージを受信するポート番号です。 以下のような行が表示されるはずです。
 
 ```shell
 $ Forwarding    http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
index 0e0ff12970..1ecc7be313 100644
--- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,5 +9,6 @@ children:
   - /managing-discussions-in-your-repository
   - /managing-categories-for-discussions-in-your-repository
   - /moderating-discussions
+  - /viewing-insights-for-your-discussions
 ---
 
diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
new file mode 100644
index 0000000000..22f5346350
--- /dev/null
+++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -0,0 +1,34 @@
+---
+title: Viewing insights for your discussions
+intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.'
+permissions: Repository administrators and people with maintain access to a repository can view the discussions insights dashboard.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Discussions
+shortTitle: View discussions insights
+---
+
+## About the discussions insights dashboard
+
+You can use discussions insights to help understand the contribution activity, page views, and growth of your repository's discussions community.
+- **Contribution activity** shows the count of total contributions to discussions, issues, and pull requests.
+- **Discussions page views** shows the total page views for discussions, segmented by logged in versus anonymous viewers.
+- **Discussions daily contributors** shows the daily count of unique users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
+- **Discussions new contributors** shows the daily count of unique new users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
+
+![Screenshot of the discussions dashboard](/assets/images/help/discussions/discussions-dashboard.png)
+
+{% tip %}
+
+**Tip:** To view the exact data for a time period, hover over that time period in the graph.
+
+{% endtip %}
+
+## Viewing discussions insights
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+3. 左のサイドバーで **[Community]** をクリックします。 ![Screenshot of the "Community" tab in left sidebar](/assets/images/help/graphs/graphs-sidebar-community-tab.png)
+1. Optionally, in the upper-right corner of the page, select the **Period** dropdown menu and click the time period for which you want to view data: **30 days**, **3 months**, or **1 year**. ![Screenshot of the date range selector for discussions insights](/assets/images/help/discussions/discussions-dashboard-date-selctor.png)
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
new file mode 100644
index 0000000000..fef163b17b
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
@@ -0,0 +1,35 @@
+---
+title: About GitHub Marketplace
+intro: '{% data variables.product.prodname_marketplace %} contains tools that add functionality and improve your workflow.'
+redirect_from:
+  - /articles/about-github-marketplace
+  - /github/customizing-your-github-workflow/about-github-marketplace
+  - /github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace  
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
+
+If you purchase a paid tool, you'll pay for your tool subscription with the same billing information you use to pay for your {% data variables.product.product_name %} subscription, and receive one bill on your regular billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+You may also have the option to select a free 14-day trial on some tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+## Finding tools on {% data variables.product.prodname_marketplace %}
+
+You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)."
+
+{% data reusables.actions.actions-not-verified %}
+
+Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)."
+
+## Building and listing a tool on {% data variables.product.prodname_marketplace %}
+
+For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)."
+
+## Further reading
+
+- "[Purchasing and installing apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)"
+- "[Managing billing for {% data variables.product.prodname_marketplace %} apps](/articles/managing-billing-for-github-marketplace-apps)"
+- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)"
+- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)"
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
new file mode 100644
index 0000000000..a6f3948d91
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -0,0 +1,43 @@
+---
+title: インテグレーションについて
+intro: 'インテグレーションは、ワークフローを補い、拡張するために{% data variables.product.product_name %}と接続されるツールとサービスです。'
+redirect_from:
+  - /articles/about-integrations
+  - /github/customizing-your-github-workflow/about-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/about-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+インテグレーションは、個人アカウントおよび自分が所有する Organization にインストールできます。 You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization.
+
+## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+
+Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs or webhooks.
+
+{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app.
+
+詳しい情報については、以下を参照してください。
+- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
+- [アプリケーションについて](/apps/about-apps/)
+- 「[ユーザレベルの権限](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)」
+- 「[{% data variables.product.prodname_oauth_apps %} を認可する](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)」
+- 「[{% data variables.product.prodname_github_apps %} を認可する](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)」
+- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations/)"
+
+インテグレーターあるいはアプリケーションの作者が {% data variables.product.prodname_github_app %} マニフェストフローでアプリケーションを作成している場合、事前設定された {% data variables.product.prodname_github_app %} をインストールできます。 自動化された設定で {% data variables.product.prodname_github_app %} を動作させる方法に関する詳しい情報については、インテグレーターもしくはアプリケーションの作者に問い合わせてください。
+
+Probot でアプリケーションをビルドしたなら、単純化された設定で {% data variables.product.prodname_github_app %} を作成できます。 詳細は [Probot docs](https://probot.github.io/docs/) を参照してください。
+
+## {% data variables.product.prodname_marketplace %}でインテグレーションを見つける
+
+{% data variables.product.prodname_marketplace %}では、インストールするインテグレーションを見つけたり、独自のインテグレーションを公開したりできます。
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. インテグレーションを探したり、独自のインテグレーションを作成することについて、詳しい情報は[{% data variables.product.prodname_marketplace %}について](/articles/about-github-marketplace)を参照してください。
+
+## インテグレータから直接購入したインテグレーション
+
+インテグレーターから直接購入できるインテグレーションもあります。 Organization のメンバーとして、使いたい {% data variables.product.prodname_github_app %} を見つけた場合は、Organization の承認をリクエストして、そのアプリケーションを Organization にインストールできます。
+
+If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. インテグレーターがアプリケーションの権限を変更した場合、その権限がリポジトリ専用であれば、Organization のオーナーとアプリケーションがインストールされているリポジトリへの管理者権限を持っている人は、新しい権限をレビューして受諾することができます。
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
new file mode 100644
index 0000000000..82fc162fba
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
@@ -0,0 +1,32 @@
+---
+title: webhook について
+redirect_from:
+  - /post-receive-hooks
+  - /articles/post-receive-hooks
+  - /articles/creating-webhooks
+  - /articles/about-webhooks
+  - /github/extending-github/about-webhooks
+intro: webhook は、特定のアクションがリポジトリあるいは Organization で生じたときに外部の Web サーバーへ通知を配信する方法を提供します。
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% tip %}
+
+**ヒント:** {% data reusables.organizations.owners-and-admins-can %}は Organization の webhook を管理します。 {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+webhook は、リポジトリあるいは Organization にさまざまなアクションが行われたときに動作します。 たとえば以下のような場合に動作するよう webhook を設定できます:
+
+* リポジトリへのプッシュ
+* プルリクエストのオープン
+* {% data variables.product.prodname_pages %}サイトの構築
+* Team への新しいメンバーの追加
+
+Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
+
+新しい webhook をセットアップするには、外部サーバーにアクセスでき、関連する技術的な手順に精通している必要があります。 関連付けられるアクションの完全なリストを含む、webhook の作成に関するヘルプについては、「[ webhook](/webhooks)」を参照してください。
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
new file mode 100644
index 0000000000..0e25673400
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -0,0 +1,55 @@
+---
+title: GitHub の機能拡張およびインテグレーション
+intro: 'サードパーティアプリケーションの中でシームレスに{% data variables.product.product_name %}リポジトリ内で作業をするために、{% data variables.product.product_name %}機能拡張を使ってください。'
+redirect_from:
+  - /articles/about-github-extensions-for-third-party-applications
+  - /articles/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Extensions & integrations
+---
+
+## エディタツール
+
+Atom、Unity、Visual Studio などのサードパーティのエディタツール内で {% data variables.product.product_name %} リポジトリに接続できます。
+
+### {% data variables.product.product_name %} for Atom
+
+{% data variables.product.product_name %} for Atom機能拡張を使うと、Atomエディタからコミット、プッシュ、プル、マージコンフリクトの解決などが行えます。 詳しい情報については公式の[{% data variables.product.product_name %} for Atomサイト](https://github.atom.io/)を参照してください。
+
+### {% data variables.product.product_name %} for Unity
+
+{% data variables.product.product_name %} for Unityエディタ機能拡張を使うと、オープンソースのゲーム開発プラットフォームであるUnity上で開発を行い、作業内容を{% data variables.product.product_name %}上で見ることができます。 詳しい情報については公式のUnityエディタ機能拡張[サイト](https://unity.github.com/)あるいは[ドキュメンテーション](https://github.com/github-for-unity/Unity/tree/master/docs)を参照してください。
+
+### {% data variables.product.product_name %} for Visual Studio
+
+{% data variables.product.product_name %} for Visual Studio機能拡張を使うと、Visual Studioから離れることなく{% data variables.product.product_name %}リポジトリ内で作業できます。 詳しい情報については、公式のVisual Studio機能拡張の[サイト](https://visualstudio.github.com/)あるいは[ドキュメンテーション](https://github.com/github/VisualStudio/tree/master/docs)を参照してください。
+
+### {% data variables.product.prodname_dotcom %} for Visual Studio Code
+
+{% data variables.product.prodname_dotcom %} for Visual Studio Code 機能拡張を使うと、Visual Studio Code の {% data variables.product.product_name %} プルリクエストをレビューおよび管理できます。 詳しい情報については、公式の Visual Studio Code 機能拡張[サイト](https://vscode.github.com/)または[ドキュメンテーション](https://github.com/Microsoft/vscode-pull-request-github)を参照してください。
+
+## プロジェクト管理ツール
+
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
+
+### Jira Cloud と {% data variables.product.product_name %}.com の統合
+
+Jira Cloud を個人または Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。 詳細については、Marketplace の[Jira 統合アプリケーション](https://github.com/marketplace/jira-software-github)にアクセスしてください。
+
+## チームコミュニケーションツール
+
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
+
+### Slack と {% data variables.product.product_name %} の統合
+
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack.
+
+The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). 詳細については、Marketplace の[Slack 統合アプリケーション](https://github.com/marketplace/slack-github)にアクセスしてください。
+
+### Microsoft Teams と {% data variables.product.product_name %} の統合
+
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. 詳細については、Microsoft AppSource の [Microsoft Teams 統合アプリケーション](https://appsource.microsoft.com/en-us/product/office/WA200002077)にアクセスしてください。
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
new file mode 100644
index 0000000000..ac84ae0e2d
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
@@ -0,0 +1,18 @@
+---
+title: インテグレーションに触れる
+intro: '{% data variables.product.product_name %} コミュニティによって構築されたツールやサービスを使用して、{% data variables.product.product_name %} のワークフローをカスタマイズしたり拡張したりできます。'
+redirect_from:
+  - /articles/exploring-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-integrations
+  - /about-webhooks
+  - /about-github-marketplace
+  - /github-extensions-and-integrations
+---
+
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/index.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/index.md
new file mode 100644
index 0000000000..fb2a794c88
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/index.md
@@ -0,0 +1,17 @@
+---
+title: GitHub ワークフローをカスタマイズする
+intro: 'Learn how you can customize your {% data variables.product.prodname_dotcom %} workflow with extensions, integrations, {% data variables.product.prodname_marketplace %}, and webhooks.'
+redirect_from:
+  - /categories/customizing-your-github-workflow
+  - /github/customizing-your-github-workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: '*'
+  ghes: '*'
+children:
+  - /exploring-integrations
+  - /purchasing-and-installing-apps-in-github-marketplace
+shortTitle: Customize your workflow
+---
+
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
new file mode 100644
index 0000000000..f71b9b32db
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
@@ -0,0 +1,15 @@
+---
+title: GitHub Marketplace でのアプリケーションの購入とインストール
+intro: '{% data variables.product.prodname_marketplace %}には、無料及び有料の価格プランのアプリケーションが含まれます。 個人アカウントまたは Organization で使用したい有料アプリケーションがある場合は、既存の支払い情報を使ってアプリケーションを購入し、インストールすることができます。'
+redirect_from:
+  - /articles/purchasing-and-installing-apps-in-github-marketplace
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /installing-an-app-in-your-personal-account
+  - /installing-an-app-in-your-organization
+shortTitle: Install Marketplace apps
+---
+
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
new file mode 100644
index 0000000000..895a581c8b
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: Organization でアプリケーションをインストールする
+intro: '{% data variables.product.prodname_marketplace %}から、Organization で使うアプリケーションをインストールできます。'
+redirect_from:
+  - /articles/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Install app organization
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+有料プランを選択している場合は、Organization のこれまでの支払い方法を使って、現在の請求日にアプリケーション プランの料金を支払います。
+
+{% data reusables.marketplace.free-trials %}
+
+## Organization で {% data variables.product.prodname_github_app %}をインストールする
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. アプリケーションでリポジトリにアクセスする必要がある場合は、すべてのリポジトリへのアクセスを許可するか、特定のリポジトリへのアクセスのみを許可するかに応じて、[**All repositories**] または [**Only select repositories**] を選択します。 ![すべてのリポジトリまたは特定のリポジトリにアプリをインストールするオプションを備えたラジオボタン](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## Organization で {% data variables.product.prodname_oauth_app %} をインストールする
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 個人アカウント、Organization、データに対するアプリケーションのアクセスについての情報を確認し、[**Authorize application**] をクリックします。
+
+## 参考リンク
+
+- [Organization の支払いプランをアップグレードする](/articles/updating-your-organization-s-payment-method)
+- 「[個人アカウントでアプリケーションをインストールする](/articles/installing-an-app-in-your-personal-account)」
diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
new file mode 100644
index 0000000000..fabcbc3e6d
--- /dev/null
+++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -0,0 +1,49 @@
+---
+title: 個人アカウントでアプリケーションをインストールする
+intro: '{% data variables.product.prodname_marketplace %} から、個人アカウントで使うアプリケーションをインストールできます。'
+redirect_from:
+  - /articles/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Install app user account
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+有料プランを使用している場合は、個人アカウントのこれまでの支払い方法を使って、現在の請求日にアプリケーション プランの料金を支払います。
+
+{% data reusables.marketplace.free-trials %}
+
+## 個人アカウントで {% data variables.product.prodname_github_app %} をインストールする
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. すべてのリポジトリへのアクセスを許可するか、特定のリポジトリへのアクセスのみを許可するかに応じて、[**All repositories**] または [**Only select repositories**] を選択します。 ![すべてのリポジトリまたは特定のリポジトリにアプリをインストールするオプションを備えたラジオボタン](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## 個人アカウントで {% data variables.product.prodname_oauth_app %}をインストールする
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 個人アカウントおよびデータに対するアプリケーションのアクセスについての情報を確認し、[**Authorize application**] をクリックします。
+
+## 参考リンク
+
+- 「[個人アカウントの支払い方法を更新する](/articles/updating-your-personal-account-s-payment-method)」
+- 「[Organization でアプリケーションをインストールする](/articles/installing-an-app-in-your-organization)」
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index f1911f0b3c..5d4cec10c0 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -49,7 +49,7 @@ shortTitle: Associate text editors
 ## エディタとして TextMate を使う
 
 1. [TextMate](https://macromates.com/) をインストールします。
-2. TextMate の `mate` のシェルユーティリティをインストールします。 詳細は、TextMate のドキュメンテーションで「[mate と rmate](https://macromates.com/blog/2011/mate-and-rmate/)」を参照してください。
+2. TextMate の `mate` のシェルユーティリティをインストールします。 For more information, see "[`mate` and `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
 {% data reusables.command_line.open_the_multi_os_terminal %}
 4. 以下のコマンドを入力してください:
   ```shell
diff --git a/translations/ja-JP/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md b/translations/ja-JP/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
index b74177574e..c21334b02f 100644
--- a/translations/ja-JP/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
+++ b/translations/ja-JP/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
@@ -12,15 +12,15 @@ versions:
 shortTitle: Properties supported by GitHub
 ---
 
-## Executable ファイル (svn:executable)
+## Executable files (`svn:executable`)
 
 Git リポジトリに追加する前に、ファイルモードを直接更新することで、`svn:executable` プロパティを変換します。
 
-## MIME タイプ (svn:mime-type)
+## MIME types (`svn:mime-type`)
 
 {% data variables.product.product_name %}は、ファイルの MIME タイププロパティ、およびそれを追加したコミットを追跡します。
 
-## バージョンのないアイテムを無視する (svn:ignore)
+## Ignoring unversioned items (`svn:ignore`)
 
 Subversion で無視されるようにファイルとディレクトリを設定している場合、{% data variables.product.product_name %} はそれらを内部的に追跡します。 Subversion のクライアントで無視されたファイルは、*.gitignore* ファイルのエントリとは全く別のものです。
 
diff --git a/translations/ja-JP/content/get-started/index.md b/translations/ja-JP/content/get-started/index.md
index 07548ee9e9..096cd5685b 100644
--- a/translations/ja-JP/content/get-started/index.md
+++ b/translations/ja-JP/content/get-started/index.md
@@ -62,6 +62,7 @@ children:
   - /exploring-projects-on-github
   - /getting-started-with-git
   - /using-git
+  - /customizing-your-github-workflow
   - /privacy-on-github
 ---
 
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index b25319a644..1dcef336fd 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -12,7 +12,7 @@ shortTitle: GitHub AE trial
 
 You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
-- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
+- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the deployment of {% data variables.product.prodname_ghe_managed %}.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
 ## {% data variables.product.prodname_ghe_managed %} のトライアルを設定する
@@ -39,24 +39,24 @@ The email address you entered above will receive instructions on how to access y
 
 {% note %}
 
-**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} instance are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
+**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} deployment are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
 
 {% endnote %}
 
 ## Navigating to your enterprise
 
-You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
+You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} deployment. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} deployments in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
 1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
 ## 次のステップ
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
+Once your deployment has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
 
 ## トライアルを終了する
 
-You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
+You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the deployment is automatically deleted.
 
 {% data variables.product.prodname_ghe_managed %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
 
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 4060caeea3..28ba3d7557 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -25,11 +25,9 @@ shortTitle: Enterprise Cloud trial
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
-{% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
 
-{% data reusables.enterprise-accounts.emu-short-summary %}
-
-{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+{% data variables.product.prodname_ghe_server %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-server)」を参照してください。
 
 {% data reusables.products.which-product-to-use %}
 
@@ -39,7 +37,11 @@ You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe
 
 トライアルには50シートが含まれています。 {% data variables.product.prodname_ghe_cloud %} を評価するためにより多くのシートが必要な場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 トライアルの終了時に、別のシート数を選択できます。
 
-{% data variables.product.prodname_ghe_server %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-server)」を参照してください。
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
 
 ## {% data variables.product.prodname_ghe_cloud %} のトライアルを設定する
 
@@ -60,11 +62,13 @@ Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be
 
 ## トライアルを終了する
 
-トライアル期間中はいつでも {% data variables.product.prodname_enterprise %} を購入するか、{% data variables.product.prodname_team %} にダウングレードできます。
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
 
-トライアル期間の終了までに {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入しない場合、Organization は {% data variables.product.prodname_free_team %} にダウングレードされ、これらのプライベートリポジトリから公開された {% data variables.product.prodname_pages %} サイトを含む有料の製品にのみ含まれる高度なツールや機能にアクセスできなくなります。 アップグレードする予定がない場合は、高度な機能へのアクセスを失わないように、トライアル期間の終了前にリポジトリを公開してください。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}.
 
-Organization の {% data variables.product.prodname_free_team %} にダウングレードすると、トライアル期間中に設定した SAML 設定も無効になります。 {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入すると、Organization 内のユーザーが認証できるように SAML 設定が再度有効になります。
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md b/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
index b34dd35ea1..1280d544d1 100644
--- a/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
@@ -53,7 +53,7 @@ versions:
 
 1. 関心のある別個のプロジェクトを指す新しいリモート URL を追加します。
   ```shell
-  $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
+  $ git remote add -f spoon-knife https://github.com/octocat/Spoon-Knife.git
   > Updating spoon-knife
   > warning: no common commits
   > remote: Counting objects: 1732, done.
@@ -61,7 +61,7 @@ versions:
   > remote: Total 1732 (delta 1086), reused 1558 (delta 967)
   > Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done.
   > Resolving deltas: 100% (1086/1086), done.
-  > From git://github.com/octocat/Spoon-Knife
+  > From https://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
 2. `Spoon-Knife` プロジェクトをローカルの Git プロジェクトにマージします。 こうしてもローカルではファイルはまったく変更されませんが、Git は次のステップに備えることになります。
diff --git a/translations/ja-JP/content/get-started/using-github/github-command-palette.md b/translations/ja-JP/content/get-started/using-github/github-command-palette.md
index 3c914b238d..c7a7db288f 100644
--- a/translations/ja-JP/content/get-started/using-github/github-command-palette.md
+++ b/translations/ja-JP/content/get-started/using-github/github-command-palette.md
@@ -26,10 +26,12 @@ The ability to run commands directly from your keyboard, without navigating thro
 
 ## Opening the {% data variables.product.prodname_command_palette %}
 
-Open the command palette using one of the following keyboard shortcuts:
+Open the command palette using one of the following default keyboard shortcuts:
 - Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
 - Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
+You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)."
+
 When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
 ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
@@ -42,6 +44,12 @@ When you open the command palette, it shows your location at the top left and us
 
 {% endnote %}
 
+### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
+
+
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode.
+
+![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
 ## Navigating with the {% data variables.product.prodname_command_palette %}
 
 You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
@@ -96,7 +104,7 @@ You can use the {% data variables.product.prodname_command_palette %} to run com
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. The default keyboard shortcuts to open the command palette in command mode are <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac). If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -106,6 +114,7 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 4. Use the arrow keys to highlight the command you want and use <kbd>Enter</kbd> to run it.
 
+
 ## Closing the command palette
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
@@ -113,6 +122,8 @@ When the command palette is active, you can use one of the following keyboard sh
 - Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
 - Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.
+
 ## {% data variables.product.prodname_command_palette %} reference
 
 ### Keystroke functions
diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
index b2e05b0d26..faad14e9fc 100644
--- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
@@ -30,48 +30,48 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 
 | キーボードショートカット                  | 説明                                                                                                                                                                                                                                                                               |
 | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>s</kbd> または <kbd>/</kbd> | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。                                                                                                           |
-| <kbd>g</kbd> <kbd>n</kbd>     | 通知に移動します。 詳しい情報については、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 |
-| <kbd>esc</kbd>                | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします                                                                                                                                                                                                         |
+| <kbd>S</kbd> または <kbd>/</kbd> | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。                                                                                                           |
+| <kbd>G</kbd> <kbd>N</kbd>     | 通知に移動します。 詳しい情報については、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 |
+| <kbd>Esc</kbd>                | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします                                                                                                                                                                                                         |
 
 {% if command-palette %}
 
-<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
 ## リポジトリ
 
 | キーボードショートカット              | 説明                                                                                                                                                                                                                            |
 | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>g</kbd> <kbd>c</kbd> | [**Code**] タブに移動します                                                                                                                                                                                                           |
-| <kbd>g</kbd> <kbd>i</kbd> | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。                                                                                                                                                    |
-| <kbd>g</kbd> <kbd>p</kbd> | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。"{% ifversion fpt or ghes or ghec %}
-| <kbd>g</kbd> <kbd>a</kbd> | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %}
-| <kbd>g</kbd> <kbd>b</kbd> | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。                                                                                                                                       |
-| <kbd>g</kbd> <kbd>w</kbd> | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
-| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
+| <kbd>G</kbd> <kbd>C</kbd> | [**Code**] タブに移動します                                                                                                                                                                                                           |
+| <kbd>G</kbd> <kbd>I</kbd> | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。                                                                                                                                                    |
+| <kbd>G</kbd> <kbd>P</kbd> | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。"{% ifversion fpt or ghes or ghec %}
+| <kbd>G</kbd> <kbd>A</kbd> | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %}
+| <kbd>G</kbd> <kbd>B</kbd> | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。                                                                                                                                       |
+| <kbd>G</kbd> <kbd>W</kbd> | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
+| <kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ## ソースコード編集
 
-| キーボードショートカット                                                    | 説明                                                                                                                                                                            |
-| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
-| <kbd>から実行されます。</kbd>                                            | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
-| <kbd>control b</kbd> または <kbd>command b</kbd>                   | 太字テキストの Markdown 書式を挿入します                                                                                                                                                     |
-| <kbd>control i</kbd> または <kbd>command i</kbd>                   | イタリック体のテキストの Markdown 書式を挿入します                                                                                                                                                |
-| <kbd>control k</kbd> または <kbd>command k</kbd>                   | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>        | Inserts Markdown formatting for an ordered list                                                                                                                               |
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>        | Inserts Markdown formatting for an unordered list                                                                                                                             |
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>         | Inserts Markdown formatting for a quote{% endif %}
-| <kbd>e</kbd>                                                    | [**Edit file**] タブでソースコードファイルを開きます                                                                                                                                            |
-| <kbd>control f</kbd> または <kbd>command f</kbd>                   | ファイルエディタで検索を開始します                                                                                                                                                             |
-| <kbd>control g</kbd> または <kbd>command g</kbd>                   | 次を検索します                                                                                                                                                                       |
-| <kbd>control shift g</kbd> or <kbd>command shift g</kbd>        | 前を検索します                                                                                                                                                                       |
-| <kbd>control shift f</kbd> or <kbd>command option f</kbd>       | 置き換えます                                                                                                                                                                        |
-| <kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | すべてを置き換えます                                                                                                                                                                    |
-| <kbd>alt g</kbd>                                                | 行にジャンプします                                                                                                                                                                     |
-| <kbd>control z</kbd> または <kbd>command z</kbd>                   | 元に戻します                                                                                                                                                                        |
-| <kbd>control y</kbd> または <kbd>command y</kbd>                   | やり直します                                                                                                                                                                        |
-| <kbd>command shift p</kbd>                                      | [**Edit file**] タブと [**Preview changes**] タブを切り替えます                                                                                                                           |
-| <kbd>control s</kbd> or <kbd>command s</kbd>                    | Write a commit message                                                                                                                                                        |
+| キーボードショートカット                                                                                                                                    | 説明                                                                                                                                                                            |
+| ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| <kbd>から実行されます。</kbd>                                                                                                                            | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                                     | 太字テキストの Markdown 書式を挿入します                                                                                                                                                     |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                                     | イタリック体のテキストの Markdown 書式を挿入します                                                                                                                                                |
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                     | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux)                   | Inserts Markdown formatting for an ordered list                                                                                                                               |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux)                   | Inserts Markdown formatting for an unordered list                                                                                                                             |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux)                   | Inserts Markdown formatting for a quote{% endif %}
+| <kbd>E</kbd>                                                                                                                                    | [**Edit file**] タブでソースコードファイルを開きます                                                                                                                                            |
+| <kbd>Command</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>F</kbd> (Windows/Linux)                                                     | ファイルエディタで検索を開始します                                                                                                                                                             |
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                                     | 次を検索します                                                                                                                                                                       |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Windows/Linux)                   | 前を検索します                                                                                                                                                                       |
+| <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F</kbd> (Windows/Linux)                  | 置き換えます                                                                                                                                                                        |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>R</kbd> (Windows/Linux) | すべてを置き換えます                                                                                                                                                                    |
+| <kbd>Alt</kbd>+<kbd>G</kbd>                                                                                                                     | 行にジャンプします                                                                                                                                                                     |
+| <kbd>Command</kbd>+<kbd>Z</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Z</kbd> (Windows/Linux)                                                     | 元に戻します                                                                                                                                                                        |
+| <kbd>Command</kbd>+<kbd>Y</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Y</kbd> (Windows/Linux)                                                     | やり直します                                                                                                                                                                        |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>                                                                                                | [**Edit file**] タブと [**Preview changes**] タブを切り替えます                                                                                                                           |
+| <kbd>Command</kbd>+<kbd>S</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>S</kbd> (Windows/Linux)                                                     | Write a commit message                                                                                                                                                        |
 
 その他のキーボードショートカットについては、[CodeMirror ドキュメント](https://codemirror.net/doc/manual.html#commands)を参照してください。
 
@@ -79,149 +79,151 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 
 | キーボードショートカット | 説明                                                                                                                 |
 | ------------ | ------------------------------------------------------------------------------------------------------------------ |
-| <kbd>t</kbd> | ファイルファインダーを起動します                                                                                                   |
-| <kbd>l</kbd> | コード内の行にジャンプします                                                                                                     |
-| <kbd>w</kbd> | 新しいブランチまたはタグに切り替えます                                                                                                |
-| <kbd>y</kbd> | URL を正規の形式に展開します。 詳細は「[ファイルにパーマリンクを張る](/articles/getting-permanent-links-to-files)」を参照してください。                      |
-| <kbd>i</kbd> | 差分に関するコメントを表示または非表示にします。 詳細は「[プルリクエストの差分についてコメントする](/articles/commenting-on-the-diff-of-a-pull-request)」を参照してください。 |
-| <kbd>a</kbd> | diff の注釈を表示または非表示にします                                                                                              |
-| <kbd>b</kbd> | blame ビューを開きます。 詳細は「[ファイル内の変更を追跡する](/articles/tracing-changes-in-a-file)」を参照してください。                                |
+| <kbd>T</kbd> | ファイルファインダーを起動します                                                                                                   |
+| <kbd>L</kbd> | コード内の行にジャンプします                                                                                                     |
+| <kbd>W</kbd> | 新しいブランチまたはタグに切り替えます                                                                                                |
+| <kbd>Y</kbd> | URL を正規の形式に展開します。 詳細は「[ファイルにパーマリンクを張る](/articles/getting-permanent-links-to-files)」を参照してください。                      |
+| <kbd>I</kbd> | 差分に関するコメントを表示または非表示にします。 詳細は「[プルリクエストの差分についてコメントする](/articles/commenting-on-the-diff-of-a-pull-request)」を参照してください。 |
+| <kbd>A</kbd> | diff の注釈を表示または非表示にします                                                                                              |
+| <kbd>B</kbd> | blame ビューを開きます。 詳細は「[ファイル内の変更を追跡する](/articles/tracing-changes-in-a-file)」を参照してください。                                |
 
 ## コメント
 
-| キーボードショートカット                                              | 説明                                                                                                                                                                                              |
-| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>control b</kbd> または <kbd>command b</kbd>             | 太字テキストの Markdown 書式を挿入します                                                                                                                                                                       |
-| <kbd>control i</kbd> または <kbd>command i</kbd>             | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>control e</kbd> or <kbd>command e</kbd>              | Inserts Markdown formatting for code or a command within a line{% endif %}
-| <kbd>control k</kbd> または <kbd>command k</kbd>             | リンクを作成するための Markdown 書式を挿入します                                                                                                                                                                   |
-| <kbd>control shift p</kbd> または <kbd>command shift p</kbd> | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>  | Inserts Markdown formatting for an ordered list                                                                                                                                                 |
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>  | Inserts Markdown formatting for an unordered list{% endif %}
-| <kbd>control enter</kbd> or <kbd>command enter</kbd>      | コメントをサブミットします                                                                                                                                                                                   |
-| <kbd>control .</kbd>、次に <kbd>control [返信テンプレート番号]</kbd>   | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>   | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
-| <kbd>control g</kbd> または <kbd>command g</kbd>             | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
+| キーボードショートカット                                                                                                                  | 説明                                                                                                                                                                                              |
+| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                   | 太字テキストの Markdown 書式を挿入します                                                                                                                                                                       |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | Inserts Markdown formatting for code or a command within a line{% endif %}
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | リンクを作成するための Markdown 書式を挿入します                                                                                                                                                                   |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list                                                                                                                                                 |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
+| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | コメントをサブミットします                                                                                                                                                                                   |
+| <kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd>                                         | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                   | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
 {% endif %}
-| <kbd>r</kbd>                                              | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。                                                                                            |
+| <kbd>R</kbd>                                                                                                                  | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)."                                               |
+
 
 ## Issue およびプルリクエストのリスト
 
-| キーボードショートカット                                  | 説明                                                                                                                                                                                                          |
-| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>c</kbd>                                  | Issueの作成                                                                                                                                                                                                    |
-| <kbd>control /</kbd> または <kbd>command /</kbd> | Issue またはプルリクエストの検索バーにカーソルを合わせます。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
-| <kbd>u</kbd>                                  | 作者によりフィルタリングします                                                                                                                                                                                             |
-| <kbd>l</kbd>                                  | ラベルによりフィルタリグするか、ラベルを編集します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                          |
-| <kbd>alt</kbd> およびクリック                        | ラベルによりフィルタリングすると同時に、ラベルを除外します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                      |
-| <kbd>m</kbd>                                  | マイルストーンによりフィルタリングするか、 マイルストーンを編集します。 詳細は「[Issue およびプルリクエストをマイルストーンでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                            |
-| <kbd>a</kbd>                                  | アサインされた人によりフィルタリングするか、 アサインされた人を編集します。 詳細は「[Issue およびプルリクエストをアサインされた人でフィルタリングする](/articles/filtering-issues-and-pull-requests-by-assignees)」を参照してください。                                                      |
-| <kbd>o</kbd> または <kbd>enter</kbd>             | Issue を開きます                                                                                                                                                                                                 |
+| キーボードショートカット                                                                                | 説明                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>C</kbd>                                                                                | Issueの作成                                                                                                                                                                                                    |
+| <kbd>Command</kbd>+<kbd>/</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows/Linux) | Issue またはプルリクエストの検索バーにカーソルを合わせます。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
+| <kbd>U</kbd>                                                                                | 作者によりフィルタリングします                                                                                                                                                                                             |
+| <kbd>L</kbd>                                                                                | ラベルによりフィルタリグするか、ラベルを編集します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                          |
+| <kbd>Alt</kbd> およびクリック                                                                      | ラベルによりフィルタリングすると同時に、ラベルを除外します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                      |
+| <kbd>M</kbd>                                                                                | マイルストーンによりフィルタリングするか、 マイルストーンを編集します。 詳細は「[Issue およびプルリクエストをマイルストーンでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                            |
+| <kbd>A</kbd>                                                                                | アサインされた人によりフィルタリングするか、 アサインされた人を編集します。 詳細は「[Issue およびプルリクエストをアサインされた人でフィルタリングする](/articles/filtering-issues-and-pull-requests-by-assignees)」を参照してください。                                                      |
+| <kbd>O</kbd> or <kbd>Enter</kbd>                                                            | Issue を開きます                                                                                                                                                                                                 |
 
 ## Issue およびプルリクエスト
-| キーボードショートカット                                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                         |
-| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>q</kbd>                                                  | レビュー担当者にリクエストします。 詳細は「[Pull Request レビューをリクエストする](/articles/requesting-a-pull-request-review/)」を参照してください。                                                                                                                                                                                                                                                                                                  |
-| <kbd>m</kbd>                                                  | マイルストーンを設定します。 詳細は「[Issue およびプルリクエストにマイルストーンを関連付ける](/articles/associating-milestones-with-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                             |
-| <kbd>l</kbd>                                                  | ラベルを適用します。 詳細は「[Issue およびプルリクエストにラベルを適用する](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                                               |
-| <kbd>a</kbd>                                                  | アサインされた人を設定します。 詳細は「[{% data variables.product.company_short %} の他のユーザに Issue およびプルリクエストをアサインする](/articles/assigning-issues-and-pull-requests-to-other-github-users/)」を参照してください。                                                                                                                                                                                                                           |
-| <kbd>cmd + shift + p</kbd> または <kbd>control + shift + p</kbd> | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
-| <kbd>alt</kbd> およびクリック                                        | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                            |
-| <kbd>shift</kbd> and click                                    | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                                |
-| <kbd>command</kbd> or <kbd>control + shift</kbd> and click    | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
+| キーボードショートカット                                                                                                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Q</kbd>                                                                                                                  | レビュー担当者にリクエストします。 詳細は「[Pull Request レビューをリクエストする](/articles/requesting-a-pull-request-review/)」を参照してください。                                                                                                                                                                                                                                                                                                        |
+| <kbd>M</kbd>                                                                                                                  | マイルストーンを設定します。 詳細は「[Issue およびプルリクエストにマイルストーンを関連付ける](/articles/associating-milestones-with-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                                   |
+| <kbd>L</kbd>                                                                                                                  | ラベルを適用します。 詳細は「[Issue およびプルリクエストにラベルを適用する](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                                                     |
+| <kbd>A</kbd>                                                                                                                  | アサインされた人を設定します。 詳細は「[{% data variables.product.company_short %} の他のユーザに Issue およびプルリクエストをアサインする](/articles/assigning-issues-and-pull-requests-to-other-github-users/)」を参照してください。                                                                                                                                                                                                                                 |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
+| <kbd>Alt</kbd> およびクリック                                                                                                        | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                                  |
+| <kbd>Shift</kbd> and click                                                                                                    | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                                      |
+| <kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux)                        | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
 
 ## プルリクエストの変更
 
-| キーボードショートカット                    | 説明                                                                                                                                                                                                                                                 |
-| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>c</kbd>                    | プルリクエスト内のコミットのリストを開きます                                                                                                                                                                                                                             |
-| <kbd>t</kbd>                    | プルリクエストで変更されたファイルのリストを開きます                                                                                                                                                                                                                         |
-| <kbd>j</kbd>                    | リストで選択を下に移動します                                                                                                                                                                                                                                     |
-| <kbd>k</kbd>                    | リストで選択を上に移動します                                                                                                                                                                                                                                     |
-| <kbd>cmd + shift + enter </kbd> | プルリクエストの差分にコメントを 1 つ追加します                                                                                                                                                                                                                          |
-| <kbd>alt</kbd> およびクリック          | `alt` を押しながら、[**Show outdated**] または [**Hide outdated**] をクリックして、期限切れのレビューコメントをすべて折りたたむか展開するかを切り替えます。|{% ifversion fpt or ghes or ghae or ghec %}
-| クリック後、<kbd>shift</kbd> およびクリック  | プルリクエストの複数行にコメントするには、行番号をクリックし、<kbd>shift</kbd> を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。
+| キーボードショートカット                                         | 説明                                                                                                                                                                                                                                                                                                               |
+| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>C</kbd>                                         | プルリクエスト内のコミットのリストを開きます                                                                                                                                                                                                                                                                                           |
+| <kbd>T</kbd>                                         | プルリクエストで変更されたファイルのリストを開きます                                                                                                                                                                                                                                                                                       |
+| <kbd>J</kbd>                                         | リストで選択を下に移動します                                                                                                                                                                                                                                                                                                   |
+| <kbd>K</kbd>                                         | リストで選択を上に移動します                                                                                                                                                                                                                                                                                                   |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | プルリクエストの差分にコメントを 1 つ追加します                                                                                                                                                                                                                                                                                        |
+| <kbd>Alt</kbd> およびクリック                               | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %}
+| Click, then <kbd>Shift</kbd> and click               | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。
 {% endif %}
 
 ## プロジェクトボード
 
 ### 列を移動する
 
-| キーボードショートカット                                                                                            | 説明                |
-| ------------------------------------------------------------------------------------------------------- | ----------------- |
-| <kbd>enter</kbd> または <kbd>space</kbd>                                                                   | フォーカスされた列を動かし始めます |
-| <kbd>escape</kbd>                                                                                       | 進行中の移動をキャンセルします   |
-| <kbd>enter</kbd>                                                                                        | 進行中の移動を完了します      |
-| <kbd>←</kbd> または <kbd>h</kbd>                                                                           | 左に列を移動します         |
-| <kbd>command + ←</kbd> または <kbd>command + h</kbd> または <kbd>control + ←</kbd> または <kbd>control + h</kbd> | 左端に列を移動します        |
-| <kbd>→</kbd> または <kbd>l</kbd>                                                                           | 右に列を移動します         |
-| <kbd>command + →</kbd> または <kbd>command + l</kbd> または <kbd>control + →</kbd> または <kbd>control + l</kbd> | 右端に列を移動します        |
+| キーボードショートカット                                                                                                                                                   | 説明                |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| <kbd>Enter</kbd> or <kbd>Space</kbd>                                                                                                                           | フォーカスされた列を動かし始めます |
+| <kbd>Esc</kbd>                                                                                                                                                 | 進行中の移動をキャンセルします   |
+| <kbd>Enter</kbd>                                                                                                                                               | 進行中の移動を完了します      |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                                                                                                   | 左に列を移動します         |
+| <kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | 左端に列を移動します        |
+| <kbd>→</kbd> or <kbd>L</kbd>                                                                                                                                   | 右に列を移動します         |
+| <kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | 右端に列を移動します        |
 
 ### カードを移動する
 
-| キーボードショートカット                                                                                                                            | 説明                  |
-| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
-| <kbd>enter</kbd> または <kbd>space</kbd>                                                                                                   | フォーカスされたカードを動かし始めます |
-| <kbd>escape</kbd>                                                                                                                       | 進行中の移動をキャンセルします     |
-| <kbd>enter</kbd>                                                                                                                        | 進行中の移動を完了します        |
-| <kbd>↓</kbd> または <kbd>j</kbd>                                                                                                           | カードを下に移動します         |
-| <kbd>command + ↓</kbd> または <kbd>command + j</kbd> または <kbd>control + ↓</kbd> または <kbd>control + j</kbd>                                 | カードを列の一番下に移動します     |
-| <kbd>↑</kbd> または <kbd>k</kbd>                                                                                                           | カードを上に移動します         |
-| <kbd>command + ↑</kbd> または <kbd>command + k</kbd> または <kbd>control + ↑</kbd> または <kbd>control + k</kbd>                                 | カードを列の一番上に移動します     |
-| <kbd>←</kbd> または <kbd>h</kbd>                                                                                                           | カードを左側の列の一番下に移動します  |
-| <kbd>shift + ←</kbd> または <kbd>shift + h</kbd>                                                                                           | カードを左側の列の一番上に移動します  |
-| <kbd>command + ←</kbd> または <kbd>command + h</kbd> または <kbd>control + ←</kbd> または <kbd>control + h</kbd>                                 | カードを一番左の列の一番下に移動します |
-| <kbd>command + shift + ←</kbd> または <kbd>command + shift + h</kbd> または <kbd>control + shift + ←</kbd> または <kbd>control + shift + h</kbd> | カードを一番左の列の一番上に移動します |
-| <kbd>→</kbd>                                                                                                                            | カードを右側の列の一番下に移動します  |
-| <kbd>shift + →</kbd> または <kbd>shift + l</kbd>                                                                                           | カードを右側の列の一番上に移動します  |
-| <kbd>command + →</kbd> または <kbd>command + l</kbd> または <kbd>control + →</kbd> または <kbd>control + l</kbd>                                 | カードを一番右の列の一番下に移動します |
-| <kbd>command + shift + →</kbd> または <kbd>command + shift + l</kbd> または <kbd>control + shift + →</kbd> または <kbd>control + shift + l</kbd> | カードを一番右の列の一番下に移動します |
+| キーボードショートカット                                                                                                                                                                                                                       | 説明                  |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
+| <kbd>Enter</kbd> or <kbd>Space</kbd>                                                                                                                                                                                               | フォーカスされたカードを動かし始めます |
+| <kbd>Esc</kbd>                                                                                                                                                                                                                     | 進行中の移動をキャンセルします     |
+| <kbd>Enter</kbd>                                                                                                                                                                                                                   | 進行中の移動を完了します        |
+| <kbd>↓</kbd> or <kbd>J</kbd>                                                                                                                                                                                                       | カードを下に移動します         |
+| <kbd>Command</kbd>+<kbd>↓</kbd> or <kbd>Command</kbd>+<kbd>J</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↓</kbd> or <kbd>Ctrl</kbd>+<kbd>J</kbd> (Windows/Linux)                                                                     | カードを列の一番下に移動します     |
+| <kbd>↑</kbd> or <kbd>K</kbd>                                                                                                                                                                                                       | カードを上に移動します         |
+| <kbd>Command</kbd>+<kbd>↑</kbd> or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↑</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                                     | カードを列の一番上に移動します     |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                                                                                                                                                                       | カードを左側の列の一番下に移動します  |
+| <kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Shift</kbd>+<kbd>H</kbd>                                                                                                                                                                     | カードを左側の列の一番上に移動します  |
+| <kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux)                                                                     | カードを一番左の列の一番下に移動します |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | カードを一番左の列の一番上に移動します |
+| <kbd>→</kbd>                                                                                                                                                                                                                       | カードを右側の列の一番下に移動します  |
+| <kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Shift</kbd>+<kbd>L</kbd>                                                                                                                                                                     | カードを右側の列の一番上に移動します  |
+| <kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux)                                                                     | カードを一番右の列の一番下に移動します |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | カードを一番右の列の一番下に移動します |
 
 ### カードをプレビューする
 
 | キーボードショートカット   | 説明               |
 | -------------- | ---------------- |
-| <kbd>esc</kbd> | カードのプレビューペインを閉じる |
+| <kbd>Esc</kbd> | カードのプレビューペインを閉じる |
 
 {% ifversion fpt or ghec %}
 ## {% data variables.product.prodname_actions %}
 
-| キーボードショートカット                                               | 説明                                   |
-| ---------------------------------------------------------- | ------------------------------------ |
-| <kbd>command + space </kbd> または <kbd>control + space</kbd> | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 |
-| <kbd>g</kbd> <kbd>f</kbd>                                  | ワークフローファイルに移動します                     |
-| <kbd>shift + t</kbd> または <kbd>T</kbd>                      | ログのタイムスタンプを切り替えます                    |
-| <kbd>shift + f</kbd> または <kbd>F</kbd>                      | フルスクリーン表示を切り替えます                     |
-| <kbd>esc</kbd>                                             | フルスクリーン表示を終了します                      |
+| キーボードショートカット                                                                                         | 説明                                   |
+| ---------------------------------------------------------------------------------------------------- | ------------------------------------ |
+| <kbd>Command</kbd>+<kbd>Space </kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Space</kbd> (Windows/Linux) | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 |
+| <kbd>G</kbd> <kbd>F</kbd>                                                                            | ワークフローファイルに移動します                     |
+| <kbd>Shift</kbd>+<kbd>T</kbd> or <kbd>T</kbd>                                                        | ログのタイムスタンプを切り替えます                    |
+| <kbd>Shift</kbd>+<kbd>F</kbd> or <kbd>F</kbd>                                                        | フルスクリーン表示を切り替えます                     |
+| <kbd>Esc</kbd>                                                                                       | フルスクリーン表示を終了します                      |
 
 {% endif %}
 
 ## 通知
 {% ifversion fpt or ghes or ghae or ghec %}
-| キーボードショートカット         | 説明           |
-| -------------------- | ------------ |
-| <kbd>e</kbd>         | 完了済としてマークします |
-| <kbd>shift + u</kbd> | 未読としてマークします  |
-| <kbd>shift + i</kbd> | 既読としてマークします  |
-| <kbd>shift + m</kbd> | サブスクライブ解除します |
+| キーボードショートカット                  | 説明           |
+| ----------------------------- | ------------ |
+| <kbd>E</kbd>                  | 完了済としてマークします |
+| <kbd>Shift</kbd>+<kbd>U</kbd> | 未読としてマークします  |
+| <kbd>Shift</kbd>+<kbd>I</kbd> | 既読としてマークします  |
+| <kbd>Shift</kbd>+<kbd>M</kbd> | サブスクライブ解除します |
 
 {% else %}
 
-| キーボードショートカット                                   | 説明           |
-| ---------------------------------------------- | ------------ |
-| <kbd>e</kbd> または <kbd>I</kbd> または <kbd>y</kbd> | 既読としてマークします  |
-| <kbd>shift + m</kbd>                           | スレッドをミュートします |
+| キーボードショートカット                                 | 説明           |
+| -------------------------------------------- | ------------ |
+| <kbd>E</kbd> or <kbd>I</kbd> or <kbd>Y</kbd> | 既読としてマークします  |
+| <kbd>Shift</kbd>+<kbd>M</kbd>                | スレッドをミュートします |
 {% endif %}
 
 ## ネットワークグラフ
 
-| キーボードショートカット                                  | 説明           |
-| --------------------------------------------- | ------------ |
-| <kbd>←</kbd> または <kbd>h</kbd>                 | 左にスクロールします   |
-| <kbd>→</kbd> または <kbd>l</kbd>                 | 右にスクロールします   |
-| <kbd>↑</kbd> または <kbd>k</kbd>                 | 上にスクロールします   |
-| <kbd>↓</kbd> または <kbd>j</kbd>                 | 下にスクロールします   |
-| <kbd>shift + ←</kbd> または <kbd>shift + h</kbd> | 左端までスクロールします |
-| <kbd>shift + →</kbd> または <kbd>shift + l</kbd> | 右端までスクロールします |
-| <kbd>shift + ↑</kbd> または <kbd>shift + k</kbd> | 上端までスクロールします |
-| <kbd>shift + ↓</kbd> または <kbd>shift + j</kbd> | 下端までスクロールします |
+| キーボードショートカット                                                                               | 説明           |
+| ------------------------------------------------------------------------------------------ | ------------ |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                               | 左にスクロールします   |
+| <kbd>→</kbd> or <kbd>L</kbd>                                                               | 右にスクロールします   |
+| <kbd>↑</kbd> or <kbd>K</kbd>                                                               | 上にスクロールします   |
+| <kbd>↓</kbd> or <kbd>J</kbd>                                                               | 下にスクロールします   |
+| <kbd>Shift</kbd>+<kbd>←</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | 左端までスクロールします |
+| <kbd>Shift</kbd>+<kbd>→</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | 右端までスクロールします |
+| <kbd>Shift</kbd>+<kbd>↑</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>K</kbd> (Windows/Linux) | 上端までスクロールします |
+| <kbd>Shift</kbd>+<kbd>↓</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>J</kbd> (Windows/Linux) | 下端までスクロールします |
diff --git a/translations/ja-JP/content/github/copilot/research-recitation.md b/translations/ja-JP/content/github/copilot/research-recitation.md
index 89da7cf6c6..e92c29a237 100644
--- a/translations/ja-JP/content/github/copilot/research-recitation.md
+++ b/translations/ja-JP/content/github/copilot/research-recitation.md
@@ -57,9 +57,9 @@ This procedure is permissive enough to let many relatively “boring” examples
 After filtering, there were 473 suggestions left. But they came in very different forms:
 
 1. Some were basically just repeats of another case that passed filtering. For example, sometimes {% data variables.product.prodname_dotcom %} Copilot makes a suggestion, the developer types a comment line, and {% data variables.product.prodname_dotcom %} Copilot offers a very similar suggestion again. I removed these cases from the analysis as duplicates.
-2. Some were long, repetitive sequences. Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> Such suggestions can be helpful (test cases, regexes) or not helpful (like this case, I suspect). But in any case, they do not fit the idea of rote learning I had in mind when I started this investigation.
+2. Some were long, repetitive sequences. Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> Such suggestions can be helpful (test cases, regular expressions) or not helpful (like this case, I suspect). But in any case, they do not fit the idea of rote learning I had in mind when I started this investigation.
 3. Some were standard inventories, like the natural numbers, or the prime numbers, or stock market tickers, or the Greek alphabet: <br>![Example of Greek alphabet](/assets/images/help/copilot/example_greek.png)
-4. Some were common, straightforward ways, perhaps even universal ways, of doing things with very few natural degrees of freedom. For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a wikipedia list. In fact, the best matching snippet found in {% data variables.product.prodname_dotcom %} Copilot's training data<sup id="anchor5">[5](#footnote5)</sup> uses such code to parse a different article and goes on to do different things with the results. <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>This doesn’t fit my idea of a quote either. It’s a bit like when someone says “I’m taking out the trash; I’ll be back soon” -- that’s a matter of fact statement, not a quote, even though that particular phrase has been uttered many times before.
+4. Some were common, straightforward ways, perhaps even universal ways, of doing things with very few natural degrees of freedom. For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a Wikipedia list. In fact, the best matching snippet found in {% data variables.product.prodname_dotcom %} Copilot's training data<sup id="anchor5">[5](#footnote5)</sup> uses such code to parse a different article and goes on to do different things with the results. <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>This doesn’t fit my idea of a quote either. It’s a bit like when someone says “I’m taking out the trash; I’ll be back soon” -- that’s a matter of fact statement, not a quote, even though that particular phrase has been uttered many times before.
 5. And then there are all other cases. Those with at least some specific overlap in either code or comments. These are what interests me most, and what I’m going to concentrate on from now on.
 
 This bucketing necessarily has some edge cases<sup id="anchor6">[6](#footnote6)</sup>, and your mileage may vary in how you think they should be classified. Maybe you even disagree with the whole set of buckets in the first place.
diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md
index 05545c00fe..db1e0bdeb6 100644
--- a/translations/ja-JP/content/github/index.md
+++ b/translations/ja-JP/content/github/index.md
@@ -12,8 +12,6 @@ versions:
   ghae: '*'
 children:
   - /copilot
-  - /customizing-your-github-workflow
-  - /extending-github
   - /site-policy
   - /site-policy-deprecated
 ---
diff --git a/translations/ja-JP/content/github/site-policy/github-government-takedown-policy.md b/translations/ja-JP/content/github/site-policy/github-government-takedown-policy.md
index b9e28b550f..ed047388f1 100644
--- a/translations/ja-JP/content/github/site-policy/github-government-takedown-policy.md
+++ b/translations/ja-JP/content/github/site-policy/github-government-takedown-policy.md
@@ -30,5 +30,8 @@ topics:
 ## gov-takedowns リポジトリに通知を投稿することの意味
 リポジトリに通知を投稿することは、そこに示されたデータについての通知を当社が受け取ったことを意味します。 これは、コンテンツが違法であるとか誤っているということを意味*しません*。 また、通知に示されたユーザが何か誤った行為を行ったということも意味*しません*。 当社は、削除を要請する当局による主張の正しさについて、いかなる判断をも下さず、またそれを暗示することもしません。 当社はこれらの通知や要請を、情報提供のみを目的として投稿しています。
 
+## Government takedowns based on violations of GitHub's Terms of Service
+In some cases, GitHub receives reports from government officials of violations of GitHub's Terms of Service. We process those violations as we would process a Terms-of-Service violation reported by anyone else. However, we notify the affected users that the report came from a government and, as with any other case, allow them the opportunity to appeal.
+
 ## 透明性レポート
-行政機関による削除要請の通知を gov-takedowns に投稿することに加え、当社はそれらを透明性レポートにおいて報告しています。 また、当社は GitHub 利用規約の侵害に基づいた行政機関による削除要請を、透明性レポートにおいて追跡・報告しています。 当社は、利用規約の侵害について、他の人々からの利用規約侵害についての報告と同様に対処します。
+In addition to posting government takedown notices in our `github/gov-takedowns` repository, we report on them in our transparency report. また、当社は GitHub 利用規約の侵害に基づいた行政機関による削除要請を、透明性レポートにおいて追跡・報告しています。
diff --git a/translations/ja-JP/content/issues/index.md b/translations/ja-JP/content/issues/index.md
index d4a2053f00..18734074fe 100644
--- a/translations/ja-JP/content/issues/index.md
+++ b/translations/ja-JP/content/issues/index.md
@@ -33,6 +33,7 @@ featuredLinks:
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
   videosHeading: GitHub Universe 2021 videos
+product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
 layout: product-landing
 beta_product: false
 versions:
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-task-lists.md
index 17aeeea223..56955693ee 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -76,5 +76,5 @@ topics:
 
 ## 参考リンク
 
-* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% if code-scanning-task-lists %}
 * "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 6340d8fc1d..cb8a2f6192 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -143,7 +143,7 @@ Issueをオープンするのにクエリパラメータを利用できます。
 | `projects`  | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` は、"Bug fix" というタイトルを付けて Issue を作成し、それを Organization のプロジェクトボード 1 に追加します。                                                                                                                                                                                              |
 | `template`  | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` は、ボディにテンプレートを付けて Issue を作成します。 `template`クエリパラメータは、ルート内の`ISSUE_TEMPLATE`サブディレクトリ、リポジトリ内の`docs/`あるいは`.github/`ディレクトリに保存されたテンプレートで動作します。 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。 |
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
index 7b7c47bb2c..e5bf914974 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
@@ -1,6 +1,6 @@
 ---
 title: Organization を安全に保つ
-intro: 'Organization のオーナーがプロジェクトとデータを安全に保つ方法はいくつかあります。 Organization のオーナーは、不正な、または悪意のあるアクティビティが発生していないことを確認するために、Organization の監査ログ{% ifversion not ghae %}、メンバーの 2 要素認証ステータス、{% endif %} そしてアプリケーション設定を定期的にレビューする必要があります。'
+intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -14,14 +14,8 @@ topics:
   - Organizations
   - Teams
 children:
-  - /viewing-whether-users-in-your-organization-have-2fa-enabled
-  - /preparing-to-require-two-factor-authentication-in-your-organization
-  - /requiring-two-factor-authentication-in-your-organization
-  - /managing-security-and-analysis-settings-for-your-organization
-  - /managing-allowed-ip-addresses-for-your-organization
-  - /restricting-email-notifications-for-your-organization
-  - /reviewing-the-audit-log-for-your-organization
-  - /reviewing-your-organizations-installed-integrations
+  - /managing-two-factor-authentication-for-your-organization
+  - /managing-security-settings-for-your-organization
 shortTitle: Organizationのセキュリティ
 ---
 
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
new file mode 100644
index 0000000000..e309d13fff
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your organization
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Teams
+permissions: Organization owners can access compliance reports for the organization.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "Compliance reports", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## 参考リンク
+
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
new file mode 100644
index 0000000000..6c813260f9
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing security settings for your organization
+shortTitle: Manage security settings
+intro: 'You can manage security settings and review the audit log{% ifversion ghec %}, compliance reports,{% endif %} and integrations for your organization.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-security-and-analysis-settings-for-your-organization
+  - /managing-allowed-ip-addresses-for-your-organization
+  - /restricting-email-notifications-for-your-organization
+  - /reviewing-the-audit-log-for-your-organization
+  - /accessing-compliance-reports-for-your-organization
+  - /reviewing-your-organizations-installed-integrations
+---
+
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
new file mode 100644
index 0000000000..51c518edfa
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -0,0 +1,85 @@
+---
+title: Organization に対する許可 IP アドレスを管理する
+intro: 接続を許可される IP アドレスのリストを設定することで、Organization のアセットに対するアクセスを制限することができます。
+product: '{% data reusables.gated-features.allowed-ip-addresses %}'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 許可 IPアドレスの管理
+---
+
+Organization のオーナーは、Organization に対する許可 IP アドレスを管理できます。
+
+## 許可 IP アドレスについて
+
+特定の IP アドレスに対する許可リストを設定することで、Organization アセットへのアクセスを制限できます。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
+
+許可リストをセットアップした場合は、Organizationにインストールした{% data variables.product.prodname_github_apps %}に設定されたIPアドレスを自動的に許可リストに追加するかを選択することもできます。 {% data variables.product.prodname_github_app %}の作者は、自分のアプリケーションのための許可リストを、アプリケーションが実行されるIPアドレスを指定して設定できます。 それらの許可リストを継承すれば、アプリケーションからの接続リクエストが拒否されるのを避けられます。 詳しい情報については「[{% data variables.product.prodname_github_apps %}によるアクセスの許可](#allowing-access-by-github-apps)」を参照してください。
+
+Enterprise アカウントで Organization に対して許可される IP アドレスを設定することもできます。 詳しい情報については、「[Enterprise にセキュリティ設定のポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)」以下を参照してください。
+
+## 許可 IP アドレスを追加する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+
+## 許可 IP アドレスを有効化する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. [**Save**] をクリックします。
+
+## {% data variables.product.prodname_github_apps %}によるアクセスの許可
+
+許可リストを使っているなら、Organizationにインストールした{% data variables.product.prodname_github_apps %}に設定されたIPアドレスを自動的に許可リストに追加するかも選択できます。
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+作成した{% data variables.product.prodname_github_app %}に許可リストを作成する方法に関する詳しい情報については「[GitHub Appに対して許可されたIPアドレスの管理](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)」を参照してください。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. "IP allow list（IP許可リスト）"の下で、**Enable IP allow list configuration for installed GitHub Apps（インストールされたGitHub AppsのIP許可リスト設定の有効化）**を選択してください。 ![GitHub AppにIPアドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. [**Save**] をクリックします。
+
+## 許可 IP アドレスを編集する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+1. [**Update**] をクリックします。
+
+## 許可 IP アドレスを削除する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## IP許可リストで {% data variables.product.prodname_actions %} を使用する
+
+{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
new file mode 100644
index 0000000000..b74dea1f52
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -0,0 +1,171 @@
+---
+title: Organization のセキュリティおよび分析設定を管理する
+intro: '{% data variables.product.prodname_dotcom %} 上の Organization のプロジェクトでコードを保護し分析する機能を管理できます。'
+permissions: Organization owners can manage security and analysis settings for repositories in the organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: セキュリティと分析の管理
+---
+
+## セキュリティおよび分析設定の管理について
+
+{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% ifversion ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合は、これらの機能へのアクセスを管理することもできます。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## セキュリティと分析の設定を表示する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+
+表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。
+
+{% ifversion ghec %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Enterprise に属している場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
+
+{% ifversion ghes > 3.0 %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれています。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
+
+{% ifversion ghae %}このページには、{% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
+
+## すべての既存のリポジトリに対して機能を有効化または無効化する
+
+すべてのリポジトリの機能を有効化または無効化できます。
+{% ifversion fpt or ghec %}変更が Organization 内のリポジトリに与える影響は、リポジトリの可視性によって決まります。
+
+- **依存関係グラフ** - この機能はパブリックリポジトリに対して常に有効になっているため、変更はプライベートリポジトリにのみ影響します。
+- **{% data variables.product.prodname_dependabot_alerts %}** - 変更はすべてのリポジトリに影響します。
+- **{% data variables.product.prodname_dependabot_security_updates %}** - 変更はすべてのリポジトリに影響します。
+{%- ifversion ghec %}
+- **{% data variables.product.prodname_GH_advanced_security %}** - {% data variables.product.prodname_GH_advanced_security %} および関連機能は常にパブリックリポジトリに対して有効になっているため、変更はプライベートリポジトリにのみ影響します。
+- **{% data variables.product.prodname_secret_scanning_caps %}** - 変更は {% data variables.product.prodname_GH_advanced_security %} も有効になっているプライベートリポジトリにのみ影響します。 {% data variables.product.prodname_secret_scanning_caps %} は常にパブリックリポジトリに対して有効になっています。
+{% endif %}
+
+{% endif %}
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+2. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 {% ifversion ghes > 3.0 or ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスにシートがない場合、「{% data variables.product.prodname_GH_advanced_security %}」の制御は無効になります。{% endif %}
+   {% ifversion fpt %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   {% endif %}
+   {% ifversion ghes > 3.2 %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。
+   {% ifversion fpt or ghec %}
+   ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![新規のリポジトリの [Enable by default] オプション](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+4. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。
+   {% ifversion fpt or ghec %}
+   ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![機能 を無効または有効にするボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion ghae or ghes > 3.0 %}
+3. **[Enable/Disable all]**あるいは**[Enable/Disable for eligible repositories]**をクリックして、変更を確認します。 ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% endif %}
+
+   {% data reusables.security.displayed-information %}
+
+## 新しいリポジトリが追加されたときに機能を自動的に有効化または無効化する
+
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+2. [Configure security and analysis features]の下で、機能の右から、Organizatin中の新しいリポジトリ{% ifversion fpt or ghec %}あるいはすべての新しいプライベートリポジトリ{% endif %}でデフォルトでその機能を有効または無効にします。
+   {% ifversion fpt %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   {% endif %}
+
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
+
+## {% data variables.product.prodname_dependabot %} のプライベート依存関係へのアクセスを許可する
+
+{% data variables.product.prodname_dependabot %} は、プロジェクト内の古い依存関係参照をチェックし、それらを更新するためのプルリクエストを自動的に生成できます。 これを行うには、{% data variables.product.prodname_dependabot %} がすべてのターゲット依存関係ファイルにアクセスできる必要があります。 通常、1 つ以上の依存関係にアクセスできない場合、バージョン更新は失敗します。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} バージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
+
+デフォルトでは、{% data variables.product.prodname_dependabot %} はプライベートリポジトリまたはプライベートパッケージレジストリにある依存関係を更新できません。 ただし、依存関係が、その依存関係を使用するプロジェクトと同じ Organization 内のプライベート {% data variables.product.prodname_dotcom %} リポジトリにある場合は、ホストリポジトリへのアクセスを許可することで、{% data variables.product.prodname_dependabot %} がバージョンを正常に更新できるようにすることができます。
+
+コードがプライベートレジストリ内のパッケージに依存している場合は、リポジトリレベルでこれを設定することにより、{% data variables.product.prodname_dependabot %} がこれらの依存関係のバージョンを更新できるようにすることができます。 これを行うには、リポジトリの _dependabot.yml_ ファイルに認証の詳細を追加します。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。
+
+{% data variables.product.prodname_dependabot %} がプライベート {% data variables.product.prodname_dotcom %} リポジトリにアクセスできるようにするには：
+
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+1. [{% data variables.product.prodname_dependabot %} private repository access] の下で、[**Add private repositories**] または [**Add internal and private repositories**] をクリックします。 ![[Add repositories] ボタン](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. 許可するリポジトリの名前を入力します。 ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png)
+1. 許可するリポジトリをクリックします。
+
+1. あるいは、リストからリポジトリを差k除するには、リポジトリの右の{% octicon "x" aria-label="The X icon" %}をクリックします。 ![リポジトリを削除する [X] ボタン](/assets/images/help/organizations/dependabot-private-repository-list.png)
+{% endif %}
+
+{% ifversion ghes > 3.0 or ghec %}
+
+## Organization 内の個々のリポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する
+
+[Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能へのアクセスを管理できます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 ただし、Organization の [Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にすることもできます。
+
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+1. {% data variables.product.prodname_GH_advanced_security %} が有効になっている Organization 内のすべてのリポジトリのリストを表示するには、「{% data variables.product.prodname_GH_advanced_security %} リポジトリ」セクションまでスクロールします。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) この表は、各リポジトリの一意のコミッターの数を示しています。 これは、{% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %}の支払いについて](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)」を参照してください。
+1. リポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除し、リポジトリ固有のコミッターが使用するシートを解放するには、隣接する {% octicon "x" aria-label="X symbol" %} をクリックします。
+1. 確認ダイアログで、[**Remove repository**] をクリックして、{% data variables.product.prodname_GH_advanced_security %} の機能へのアクセスを削除します。
+
+{% note %}
+
+**注釈:** リポジトリの {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する場合は、影響を受ける開発チームと連絡を取り、変更が意図されたものかを確認する必要があります。 これにより、失敗したコードスキャンの実行をデバッグすることに時間を費すことがなくなります。
+
+{% endnote %}
+
+{% endif %}
+
+## 参考リンク
+
+- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not fpt %}
+- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
+- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- [依存関係を自動的に更新する](/github/administering-a-repository/keeping-your-dependencies-updated-automatically){% endif %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..1befe1c69c
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,47 @@
+---
+title: Organizationのメール通知の制限
+intro: Organizationの情報が個人のメールアカウントに漏れてしまうことを避けるために、メンバーがOrganizationのアクティビティに関するメール通知を受信できるドメインを制限できます。
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '>=3.2'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: メール通知の制限
+---
+
+## メールの制限について
+
+Organization で制限付きのメール通知が有効になっている場合、メンバーは Organization の検証済みあるいは承認済みドメインに関連付けられたメールアドレスのみを使用して、Organization のアクティビティに関するメール通知を受信できます。 詳しい情報については「[Organizationのドメインの検証もしくは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+外部のコラボレーターは、検証済みあるいは承認済みドメインへのメール通知の制限の対象になりません。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+
+Enterprise アカウントがオーナーの Organization の場合、Organization のメンバーは、Organization の検証済みあるいは承認済みドメインに加えて、Enterprise アカウントの検証済みあるいは承認済みドメインから通知を受け取ることができます。 For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+
+## メール通知の制限
+
+Organizationのメール通知を制限できるようにするには、Oraganizationに対して最低1つのドメインを検証あるいは承認するか、EnterpriseのオーナーがEnterpriseアカウントに対して最低1つのドメインを検証あるいは承認しなければなりません。
+
+Organizationの検証済み及び承認済みドメインに関する詳しい情報については「[Organizationのドメインの検証もしくは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
new file mode 100644
index 0000000000..7f4197b9a5
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -0,0 +1,772 @@
+---
+title: Organization の Audit log をレビューする
+intro: Audit log により、Organization の管理者は Organization のメンバーによって行われたアクションをすばやくレビューできます。 これには、誰がいつ何のアクションを実行したかなどの詳細が残されます。
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-the-audit-log-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization
+  - /organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 監査ログのレビュー
+---
+
+## Audit log にアクセスする
+
+The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Organization の Audit log にアクセスできるのはオーナーのみです。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+
+## Audit log を検索する
+
+{% data reusables.audit_log.audit-log-search %}
+
+### 実行されたアクションに基づく検索
+
+特定のイベントを検索するには、クエリで `action` 修飾子を使用します。 Audit log に一覧表示されるアクションは以下のカテゴリに分類されます。
+
+| カテゴリ名                                                                                                                                                                                                                         | 説明                                                                                                                                                                                                                                                                                                              |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`アカウント`](#account-category-actions)                                                                                                                                                                                          | Organization アカウントに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                        |
+| [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                        | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリのコントリビューターのクレジットに関連するすべてのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。                               |
+| [`支払い`](#billing-category-actions)                                                                                                                                                                                            | Organization の支払いに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                         |
+| [`business`](#business-category-actions)                                                                                                                                                                                      | Enterpriseのビジネス設定に関連するアクティビティを含みます。                                                                                                                                                                                                                                                                             |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                  | OrganizationのCodespacesに関連するすべてのアクティビティを含みます。 |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                    | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in existing repositories. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。                               |
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.                                                                                                                                            |
+| [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                | 既存のリポジトリ内の {% data variables.product.prodname_dependabot_security_updates %} の Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。         |
+| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions)                                                                                                                            | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
+| [`dependency_graph`](#dependency_graph-category-actions)                                                                                                                                                                      | リポジトリの依存関係グラフの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。                                                                                                                                                |
+| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions)                                                                                                                                                  | Organization 内に作成された新しいリポジトリの Organization レベルの設定アクティビティが対象です。{% endif %}
+| [`discussion_post`](#discussion_post-category-actions)                                                                                                                                                                        | Team ページに投稿されたディスカッションに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                    |
+| [`discussion_post_reply`](#discussion_post_reply-category-actions)                                                                                                                                                            | Teamページにポストされたディスカッションへの返信に関連するすべてのアクティビティを含みます。{% ifversion fpt or ghes or ghec %}
+| [`Enterprise`](#enterprise-category-actions)                                                                                                                                                                                  | Enterprise設定に関連するアクティビティを含みます。                                                                                                                                                                                                                                                                                  |{% endif %}
+| [`フック`](#hook-category-actions)                                                                                                                                                                                               | webhookに関連するすべてのアクティビティを含みます。                                                                                                                                                                                                                                                                                   |
+| [`integration_installation_request`](#integration_installation_request-category-actions)                                                                                                                                      | Organization 内で使用するインテグレーションをオーナーが承認するよう求める、 Organization メンバーからのリクエストに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                    |
+| [`ip_allow_list`](#ip_allow_list)                                                                                                                                                                                             | Contains activities related to enabling or disabling the IP allow list for an organization.                                                                                                                                                                                                                     |
+| [`ip_allow_list_entry`](#ip_allow_list_entry)                                                                                                                                                                                 | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.                                                                                                                                                                                               |
+| [`Issue`](#issue-category-actions)                                                                                                                                                                                            | Issue の削除に関連するアクティビティが対象です。                                                                                                                                                                                                                                                                                     |{% ifversion fpt or ghec %}
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions)                                                                                                                                        | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。                                                                                                                                                                                                                      |
+| [`marketplace_listing`](#marketplace_listing-category-actions)                                                                                                                                                                | {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} でのアプリのリストに関連するすべてのアクティビティが対象です。                                                                                                                                                                          |
+| [`members_can_create_pages`](#members_can_create_pages-category-actions)                                                                                                                                                      | Organization 内のリポジトリの {% data variables.product.prodname_pages %} サイトの公開の管理に関連するすべてのアクティビティが対象です。 詳しい情報については「[Organizationの{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 |{% endif %}
+| [`org`](#org-category-actions)                                                                                                                                                                                                | Organizationのメンバーシップに関連するアクティビティを含みます。{% ifversion ghec %}
+| [`org_credential_authorization`](#org_credential_authorization-category-actions)                                                                                                                                              | SAML シングルサインオンで使用する認可クレデンシャルに関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
+| [`organization_label`](#organization_label-category-actions)                                                                                                                                                                  | Organization のリポジトリのデフォルトラベルに関連するすべてのアクティビティが対象です。{% endif %}
+| [`oauth_application`](#oauth_application-category-actions)                                                                                                                                                                    | OAuth アプリに関連するすべてのアクティビティが対象です。{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`パッケージ`](#packages-category-actions)                                                                                                                                                                                         | {% data variables.product.prodname_registry %} に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions)                                                                                                                                                                          | Organization の GitHub への支払い方法に関連するすべてのアクティビティが対象です。{% endif %}
+| [`profile_picture`](#profile_picture-category-actions)                                                                                                                                                                        | Organization のプロフィール画像に関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                    |
+| [`project`](#project-category-actions)                                                                                                                                                                                        | プロジェクト ボードに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                     |
+| [`protected_branch`](#protected_branch-category-actions)                                                                                                                                                                      | 保護されたブランチ関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                                  |
+| [`repo`](#repo-category-actions)                                                                                                                                                                                              | Organization が所有するリポジトリに関連するアクティビティを含みます。{% ifversion fpt or ghec %}
+| [`repository_advisory`](#repository_advisory-category-actions)                                                                                                                                                                | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリに関連するリポジトリレベルのアクティビティが対象です。  詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。                                         |
+| [`repository_content_analysis`](#repository_content_analysis-category-actions)                                                                                                                                                | [プライベート リポジトリに対するデータの使用を有効または無効にする](/articles/about-github-s-use-of-your-data)に関連するすべての活動が対象です。{% endif %}{% ifversion fpt or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions)                                                                                                                                                | プライベートリポジトリの依存関係グラフの有効化または無効化に関連する                                                                                                                                                                                                                                                                              |
+| {% ifversion fpt or ghec %}リポジトリ{% endif %}レベルのアクティビティが含まれます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。{% endif %}{% ifversion ghes or ghae or ghec %} |                                                                                                                                                                                                                                                                                                                 |
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions)                                                                                                                                                  | シークレットスキャンに関連するリポジトリレベルのアクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。                                                                                                                                                                       |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions)                                                                                                                                          | [脆弱性のある依存関係](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)の {% data variables.product.prodname_dependabot_alerts %} に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghec %}
+| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions)                                                                                                                                        | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
+| [`ロール`](#role-category-actions)                                                                                                                                                                                               | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`secret_scanning`](#secret_scanning-category-actions)                                                                                                                                                                        | 既存のリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。                                                                                                                                                      |
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions)                                                                                                                                                    | Organization で作成された新しいリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。                                                                                                                                                                                                                                       |{% endif %}{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions)                                                                                                                                                                                      | スポンサーボタンに関連するすべてのアクティビティが対象です (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %}
+| [`Team`](#team-category-actions)                                                                                                                                                                                              | Organization内のチームに関連するすべてのアクティビティを含みます。                                                                                                                                                                                                                                                                         |
+| [`team_discussions`](#team_discussions-category-actions)                                                                                                                                                                      | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| [`ワークフロー`](#workflows-category-actions)                                                                                                                                                                                       | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %}
+
+次の用語を使用すれば、特定の一連の行動を検索できます。 例:
+
+  * `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。
+  * `-action:hook` は webhook カテゴリ内のすべてのイベントを除外します。
+
+各カテゴリには、フィルタできる一連の関連アクションがあります。 例:
+
+  * `action:team.create`はTeamが作成されたすべてのイベントを検索します。
+  * `-action:hook.events_changed` は webhook の変更されたすべてのイベントを除外します。
+
+### アクション時間に基づく検索
+
+`created` 修飾子を使用して、行われた日時に基づいて Audit log 内のイベントをフィルタします。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+例:
+
+  * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。
+  * `created:>=2014-07-08` は、2014 年 7 月 8 日かそれ以降に生じたすべてのイベントを検索します。
+  * `created:<=2014-07-08`は、2014 年 7 月 8 日かそれ以前に生じたすべてのイベントを検索します。
+  * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。
+
+
+{% note %}
+
+**Note**: The audit log contains data for the current month and every day of the previous six months.
+
+{% endnote %}
+
+### 場所に基づく検索
+
+修飾子 `country` を使用すれば、発信元の国に基づいて Audit log 内のイベントをフィルタリングできます。 国の 2 文字のショートコードまたはフル ネームを使用できます。 名前に空白がある国は引用符で囲む必要があることに注意してください。 例:
+
+  * `country:de` は、ドイツで発生したイベントをすべて検索します。
+  * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。
+  * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。
+
+{% ifversion fpt or ghec %}
+## Audit log をエクスポートする
+
+{% data reusables.audit_log.export-log %}
+{% data reusables.audit_log.exported-log-keys-and-values %}
+{% endif %}
+
+## Audit log API を使用する
+
+GraphQL API{% ifversion fpt or ghec %} または REST API を使用して Audit log を操作できます{% endif %}。
+
+{% ifversion fpt or ghec %}
+The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+
+### GraphQL API を使用する
+
+{% endif %}
+
+{% note %}
+
+**注釈**: {% data variables.product.prodname_enterprise %} を使用している Organization が Audit log GraphQL API を利用できます。 {% data reusables.gated-features.more-info-org-products %}
+
+{% endnote %}
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audit-log-api-info %}
+
+{% ifversion fpt or ghec %}
+GraphQL API を使用して Git イベントを取得することはできませんので、ご注意ください。 Git イベントを取得するには、代わりに REST API を使用してください。 詳しい情報については、「[`git` category actions](#git-category-actions)」を参照してください。
+{% endif %}
+
+GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。
+
+たとえば、GraphQL にリクエストして、Organization に新しく追加された Organization メンバー全員を表示できます。 詳細は「[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)」を参照してください。
+
+{% ifversion fpt or ghec %}
+
+### REST API を使用する
+
+{% note %}
+
+**注釈:** Audit log REST API は、{% data variables.product.prodname_ghe_cloud %} のユーザのみが利用できます。
+
+{% endnote %}
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+Audit log REST API の詳細については、「[Organization](/rest/reference/orgs#get-the-audit-log-for-an-organization)」を参照してください。
+
+{% endif %}
+
+## Audit log のアクション
+
+Audit log にイベントとして記録される最も一般的なアクションの概要です。
+
+{% ifversion fpt or ghec %}
+### `account` カテゴリアクション
+
+| アクション                         | 説明                                                                                                                                                     |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `billing_plan_change`         | Organization の[支払いサイクル](/articles/changing-the-duration-of-your-billing-cycle)が変わるときにトリガーされます。                                                         |
+| `plan_change`                 | Organization の[プラン](/articles/about-billing-for-github-accounts)が変わるときにトリガーされます。                                                                       |
+| `pending_plan_change`         | Organization のオーナーまたは支払いマネージャーが[支払い済みサブスクリプションをキャンセルまたはダウングレードする](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/)ときにトリガーされます。 |
+| `pending_subscription_change` | [{% data variables.product.prodname_marketplace %} の無料トライアルが始まるか期限切れになる](/articles/about-billing-for-github-marketplace/)ときにトリガーされます。                  |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `advisory_credit` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                       |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`  | ユーザがセキュリティアドバイザリのクレジットを受け入れるとトリガーされます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 |
+| `create`  | セキュリティアドバイザリの管理者がクレジットセクションにユーザを追加するとトリガーされます。                                                                                                           |
+| `decline` | ユーザがセキュリティアドバイザリのクレジットを拒否するとトリガーされます。                                                                                                                    |
+| `destroy` | セキュリティアドバイザリの管理者がクレジットセクションからユーザを削除するとトリガーされます。                                                                                                          |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `billing` カテゴリアクション
+
+| アクション                 | 説明                                                                                                                                 |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `change_billing_type` | Organization が[{% data variables.product.prodname_dotcom %} の支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 |
+| `change_email`        | Organization の[支払い請求先メール アドレス](/articles/setting-your-billing-email)が変わるときにトリガーされます。                                               |
+{% endif %}
+
+### `business`カテゴリアクション
+
+| アクション                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Enterpriseで、パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %}
+| `set_actions_retention_limit`          | {% data variables.product.prodname_actions %}の成果物とログの保持期間がEnterpriseで変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`         | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %}
+
+{% ifversion fpt or ghec %}
+### `codespaces` カテゴリアクション
+
+| アクション                        | 説明                                                                                                                                                                                                                       |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`                     | ユーザが[Codespaceを作成](/github/developing-online-with-codespaces/creating-a-codespace)するとトリガーされます。                                                                                                                           |
+| `resume`                     | ユーザがサスペンドされたCodespaceを再開するとトリガーされます。                                                                                                                                                                                     |
+| `delete`                     | ユーザが[Codespaceを削除](/github/developing-online-with-codespaces/deleting-a-codespace)するとトリガーされます。                                                                                                                           |
+| `create_an_org_secret`       | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を作成するとトリガーされます。 |
+| `update_an_org_secret`       | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を更新するとトリガーされます。 |
+| `remove_an_org_secret`       | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を削除するとトリガーされます。 |
+| `manage_access_and_security` | ユーザが[Codespaceがアクセスできるリポジトリ](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を更新するとトリガーされます。                                                                                       |
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.2 %}
+### `dependabot_alerts` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                                                                                                                         |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                                                        |
+
+### `dependabot_alerts_new_repos` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                                                                                                                    |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                                                        |
+
+### `dependabot_security_updates` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                                                             |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。                                                                                                                                                                       |
+
+### `dependabot_security_updates_new_repos` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                                                             |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。                                                                                                                                                                       |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `dependency_graph` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                               |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。                                                                                                                                                                       |
+
+### `dependency_graph_new_repos` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                               |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 |
+| `enable`  | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。                                                                                                                                                                       |
+{% endif %}
+
+### `discussion_post` カテゴリアクション
+
+| アクション     | 説明                                                                                               |
+| --------- | ------------------------------------------------------------------------------------------------ |
+| `update`  | [Team ディスカッションの投稿が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。  |
+| `destroy` | [Team ディスカッションの投稿が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 |
+
+### `discussion_post_reply` カテゴリアクション
+
+| アクション     | 説明                                                                                                   |
+| --------- | ---------------------------------------------------------------------------------------------------- |
+| `update`  | [Team ディスカッションの投稿への返答が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。  |
+| `destroy` | [Team ディスカッションの投稿への返答が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 |
+
+{% ifversion fpt or ghes or ghec %}
+### `enterprise` カテゴリアクション
+
+{% data reusables.actions.actions-audit-events-for-enterprise %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `environment` カテゴリアクション
+
+| アクション                   | 説明                                                                                                                   |
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `create_actions_secret` | シークレットが環境で作成されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。  |
+| `delete`                | 環境が削除されるとトリガーされます。 詳しい情報については、「[環境を削除する](/actions/reference/environments#deleting-an-environment)」を参照してください。         |
+| `remove_actions_secret` | シークレットが環境で削除されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。  |
+| `update_actions_secret` | 環境内のシークレットが更新されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。 |
+{% endif %}
+
+{% ifversion ghae %}
+### `external_group` category actions
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% endif %}
+
+{% ifversion ghae %}
+### `external_identity` category actions
+
+{% data reusables.saml.external-identity-audit-events %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `git` カテゴリアクション
+
+{% note %}
+
+**注釈:** Audit log の Git イベントにアクセスするには、Audit log REST API を使用する必要があります。 Audit log REST API は、{% data variables.product.prodname_ghe_cloud %} のユーザのみが利用できます。 詳しい情報については「[Organization](/rest/reference/orgs#get-the-audit-log-for-an-organization)」を参照してください。
+
+{% endnote %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+| アクション  | 説明                          |
+| ------ | --------------------------- |
+| `クローン` | リポジトリがクローンされるとトリガーされます。     |
+| `フェッチ` | リポジトリから変更がフェッチされるとトリガーされます。 |
+| `プッシュ` | リポジトリに変更がプッシュされるとトリガーされます。  |
+
+{% endif %}
+
+### `hook` カテゴリアクション
+
+| アクション            | 説明                                                                              |
+| ---------------- | ------------------------------------------------------------------------------- |
+| `create`         | Organization が所有するリポジトリに[新たなフックが追加された](/articles/creating-webhooks)ときにトリガーされます。 |
+| `config_changed` | 既存のフックに変更された設定がある場合にトリガーされます。                                                   |
+| `destroy`        | 既存のフックがリポジトリから削除されたときにトリガーされます。                                                 |
+| `events_changed` | フックでのイベントが変更された場合にトリガーされます。                                                     |
+
+### `integration_installation_request` カテゴリアクション
+
+| アクション    | 説明                                                                                                                                 |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Organization のメンバーが、Organization 内で使用するために、Organization のオーナーにインテグレーションをインストールすることを要求するときにトリガーされます。                                |
+| `close`  | Organization 内で使用するためにインテグレーションをインストールする要求が、Organization のオーナーにより承認または拒否されるか、あるいは要求を公開した Organization のメンバーによりキャンセルされるときにトリガーされます。 |
+
+### `ip_allow_list` category actions
+
+| アクション                        | 説明                                                                                                              |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------- |
+| `enable`                     | Triggered when an IP allow list was enabled for an organization.                                                |
+| `disable`                    | Triggered when an IP allow list was disabled for an organization.                                               |
+| `enable_for_installed_apps`  | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.  |
+| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. |
+
+### `ip_allow_list_entry` category actions
+
+| アクション     | 説明                                                              |
+| --------- | --------------------------------------------------------------- |
+| `create`  | Triggered when an IP address was added to an IP allow list.     |
+| `update`  | Triggered when an IP address or its description was changed.    |
+| `destroy` | Triggered when an IP address was deleted from an IP allow list. |
+
+### `issue` カテゴリアクション
+
+| アクション     | 説明                                                                                     |
+| --------- | -------------------------------------------------------------------------------------- |
+| `destroy` | リポジトリで管理者権限を所有する Organization のオーナーまたは誰かが、Organization が所有するリポジトリから問題を削除するときにトリガーされます。 |
+
+{% ifversion fpt or ghec %}
+
+### `marketplace_agreement_signature` カテゴリアクション
+
+| アクション    | 説明                                                                                      |
+| -------- | --------------------------------------------------------------------------------------- |
+| `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 |
+
+### `marketplace_listing` カテゴリアクション
+
+| アクション     | 説明                                                                                  |
+| --------- | ----------------------------------------------------------------------------------- |
+| `承認`      | 一覧表を {% data variables.product.prodname_marketplace %}に掲載することが承認されるときにトリガーされます。     |
+| `create`  | {% data variables.product.prodname_marketplace %} で自分のアプリケーションの一覧表を作成するときにトリガーされます。 |
+| `delist`  | 一覧表が {% data variables.product.prodname_marketplace %} から削除されるときにトリガーされます。          |
+| `redraft` | 一覧表がドラフト状態に戻されるときにトリガーされます。                                                         |
+| `reject`  | 一覧表が {% data variables.product.prodname_marketplace %} に掲載することを認められないときにトリガーされます。   |
+
+{% endif %}
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+
+### `members_can_create_pages` カテゴリアクション
+
+詳しい情報については「[Organizationの{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。
+
+| アクション     | 説明                                                                                                             |
+|:--------- |:-------------------------------------------------------------------------------------------------------------- |
+| `enable`  | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を有効化するときトリガーされます。 |
+| `disable` | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を無効化するときトリガーされます。 |
+
+{% endif %}
+
+### `org` カテゴリアクション
+
+| アクション                                               | 説明                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member`                                        | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_policy_selected_member_disabled` | Enterprise のオーナーが、Organization が所有するリポジトリで {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できないようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `advanced_security_policy_selected_member_enabled`  | Enterprise のオーナーが、Organization が所有するリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できるようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %}
+| `audit_log_export`                                  | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。                                                                                                                                                                                                                                                     |
+| `block_user`                                        | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                             |
+| `cancel_invitation`                                 | Organization の招待が取り消されている場合にトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                       |{% endif %}{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                             | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。{% endif %}                                                                                                                                                                           |{% ifversion fpt or ghec %}
+| `disable_oauth_app_restrictions`                    | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `disable_saml`                                      | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %}
+| `disable_member_team_creation_permission`           | Organization のオーナーがオーナーに Team 作成を制限するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 {% ifversion not ghae %}
+| `disable_two_factor_requirement`                    | Organization のすべてのメンバー{% ifversion fpt or ghec %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を無効化するときにトリガーされます。{% endif %}{% ifversion fpt or ghec %}
+| `enable_oauth_app_restrictions`                     | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `enable_saml`                                       | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %}
+| `enable_member_team_creation_permission`            | メンバーが Team を作成するのを Organizationのオーナーが許可するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 {% ifversion not ghae %}
+| `enable_two_factor_requirement`                     | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `invite_member`                                     | [新しいユーザーがOrganization に参加するよう招待](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)されたときにトリガーされます。                                                                                                                                                                                                                                                                           |
+| `oauth_app_access_approved`                         | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。                                                                                                                                                                                                                                                                                    |
+| `oauth_app_access_denied`                           | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                |
+| `oauth_app_access_requested`                        | オーナーが Organization への {% data variables.product.prodname_oauth_app %} アクセスを許可することを Organization のメンバーが要求するときにトリガーされます。{% endif %}
+| `register_self_hosted_runner`                       | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。                                                                                                                                                                                                                          |
+| `remove_actions_secret`                             | {% data variables.product.prodname_actions %} シークレットが削除されるとトリガーされます。{% ifversion fpt or ghec %}
+| `remove_billing_manager`                            | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 
+{% endif %}
+| `remove_member`                                     | [オーナーが Organization からメンバーを削除する](/articles/removing-a-member-from-your-organization/)とき {% ifversion not ghae %}、または[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、Organization のメンバーが 2 要素認証を使用しないか 2 要素認証を無効化するとき{% endif %}にトリガーされます。 Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。               |
+| `remove_outside_collaborator`                       | オーナーが Organization から外部のコラボレータを削除するとき{% ifversion not ghae %}、または[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、外部のコラボレータが 2 要素認証を使用しないか 2 要素認証を無効化するとき{% endif %}にトリガーされます。                                                                                                                                                                                        |
+| `remove_self_hosted_runner`                         | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。                                                                                                                                                                                                                                       |{% ifversion ghec %}
+| `revoke_external_identity`                          | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。                                                                                                                          |
+| `revoke_sso_session`                                | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。                                                                                                                             |{% endif %}
+| `runner_group_created`                              | セルフホストランナーグループが作成されたときにトリガーされます。 詳しい情報については、「[Organization のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)」を参照してください。                                                                                                                                                                                  |
+| `runner_group_created`                              | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                                                       |
+| `runner_group_updated`                              | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                      |
+| `runner_group_runners_added`                        | セルフホストランナーがグループに追加されたときにトリガーされます。 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。                                                                                                                                                                                                               |
+| `runner_group_runner_removed`                       | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 詳しい情報については、「[Organization のグループからセルフホストランナーを削除する](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)」を参照してください。                                                                                                                                                                                                                         |
+| `runner_group_runners_updated`                      | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については、「[Organizationのグループにセルフホストランナーを設定する](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`                         | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                             |
+| `self_hosted_runner_offline`                        | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`                        | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy`              | Organizationで、パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 詳しい情報については「[パブリックフォークからのワークフローで承認を必須とする](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)」を参照してください。{% endif %}
+| `set_actions_retention_limit`                       | {% data variables.product.prodname_actions %}の成果物とログの保持期間が変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`                      | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 詳しい情報については「[プライベートリポジトリフォークからのワークフローの有効化](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)」を参照してください。{% endif %}{% ifversion fpt or ghec %}
+| `unblock_user`                                      | Organizationのオーナーが[ Organization からのユーザのブロックを解除](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)するときにトリガーされます。{% endif %}{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                             | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。{% endif %}
+| `update_new_repository_default_branch_setting`      | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。                                                                                                                                                                                |
+| `update_default_repository_permission`              | オーナーが Organization のメンバーのデフォルトリポジトリの権限レベルを変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                  |
+| `update_member`                                     | オーナーがユーザーのロールをオーナーからメンバーに、またはメンバーからオーナーに変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                    |
+| `update_member_repository_creation_permission`      | オーナーが Organization のメンバーのリポジトリ作成権限を変更するときにトリガーされます。{% ifversion fpt or ghec %}
+| `update_saml_provider_settings`                     | Organization の SAML プロバイダ設定が更新されるときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                               |
+| `update_terms_of_service`                           | Organization が標準利用規約と企業向け利用規約を切り替えるときにトリガーされます。 詳細は「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。{% endif %}
+
+{% ifversion ghec %}
+### `org_credential_authorization` カテゴリアクション
+
+| アクション          | 説明                                                                                                                                                                              |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grant`        | [SAML シングルサインオンに使用するクレデンシャルをメンバーが認可する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                    |
+| `deauthorized` | [SAML シングルサインオンに使用するクレデンシャルの認可をメンバーが取り消す](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                 |
+| `revoke`       | オーナーが[認可された認証情報を取り消す](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)ときにトリガーされます。 |
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghae or ghec %}
+### `organization_label` カテゴリアクション
+
+| アクション     | 説明                         |
+| --------- | -------------------------- |
+| `create`  | デフォルトラベルが作成されるときにトリガーされます。 |
+| `update`  | デフォルトラベルが編集されるときにトリガーされます。 |
+| `destroy` | デフォルトラベルが削除されるときにトリガーされます。 |
+
+{% endif %}
+
+### `oauth_application` カテゴリアクション
+
+| アクション           | 説明                                                                                         |
+| --------------- | ------------------------------------------------------------------------------------------ |
+| `create`        | 新たな {% data variables.product.prodname_oauth_app %} が作成されるときにトリガーされます。                   |
+| `destroy`       | 既存の {% data variables.product.prodname_oauth_app %} が削除されるときにトリガーされます。                   |
+| `reset_secret`  | {% data variables.product.prodname_oauth_app %} のクライアント シークレットがリセットされるときにトリガーされます。       |
+| `revoke_tokens` | {% data variables.product.prodname_oauth_app %} のユーザートークンが取り消されるときにトリガーされます。             |
+| `移譲`            | 既存の {% data variables.product.prodname_oauth_app %} が新しい Organization に移譲されるときにトリガーされます。 |
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+### `packages` カテゴリアクション
+
+| アクション                       | 説明                                                                                                                                      |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `package_version_published` | パッケージのバージョンが公開されるとトリガーされます。                                                                                                             |
+| `package_version_deleted`   | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 |
+| `package_deleted`           | パッケージ全体が削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。        |
+| `package_version_restored`  | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 |
+| `package_restored`          | パッケージ全体がリストアされるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。      |
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `payment_method` カテゴリアクション
+
+| アクション    | 説明                                                      |
+| -------- | ------------------------------------------------------- |
+| `create` | 新しいクレジット カードや PayPal アカウントなど、新たな支払い方法が追加されるときにトリガーされます。 |
+| `update` | 既存の支払い方法が更新されるときにトリガーされます。                              |
+
+{% endif %}
+
+### `profile_picture` カテゴリアクション
+| アクション  | 説明                                           |
+| ------ | -------------------------------------------- |
+| update | Organization のプロファイル写真を設定または更新するときにトリガーされます。 |
+
+### `project` カテゴリアクション
+
+| アクション                    | 説明                                                                                     |
+| ------------------------ | -------------------------------------------------------------------------------------- |
+| `create`                 | プロジェクト ボードが作成されるときにトリガーされます。                                                           |
+| `link`                   | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。                                                    |
+| `rename`                 | プロジェクトボードの名前が変更されるときにトリガーされます。                                                         |
+| `update`                 | プロジェクト ボードが更新されるときにトリガーされます。                                                           |
+| `delete`                 | プロジェクトボードが削除されるときにトリガーされます。                                                            |
+| `unlink`                 | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。                                                  |
+| `update_org_permission`  | Organization のすべてのメンバーに対して、基本レベルの権限が変更または削除されるときにトリガーされます。                             |
+| `update_team_permission` | Team のプロジェクト ボードの権限レベルが変更されるとき、または Team がプロジェクト ボードに追加または削除されるときにトリガーされます。             |
+| `update_user_permission` | Organization のメンバーまたは外部コラボレーターがプロジェクト ボードに追加または削除されるとき、または彼らの権限レベルが変更されている場合にトリガーされます。 |
+
+### `protected_branch` カテゴリアクション
+
+| アクション                                                 | 説明                                                                                                             |
+| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| `create`                                              | ブランチでブランチの保護が有効になるときにトリガーされます。                                                                                 |
+| `destroy`                                             | ブランチでブランチの保護が無効になるときにトリガーされます。                                                                                 |
+| `update_admin_enforced`                               | リポジトリの管理者に対してブランチの保護が実施されるときにトリガーされます。                                                                         |
+| `update_require_code_owner_review`                    | 必須コードオーナーレビューの実施がブランチで更新されるときにトリガーされます。                                                                        |
+| `dismiss_stale_reviews`                               | 古い Pull Request の却下の実施がブランチで更新されるときにトリガーされます。                                                                  |
+| `update_signature_requirement_enforcement_level`      | 必須コミット署名の実施がブランチで更新されるときにトリガーされます。                                                                             |
+| `update_pull_request_reviews_enforcement_level`       | 必須 Pull Request レビューの実施がブランチで更新されるときにトリガーされます。 Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). |
+| `update_required_status_checks_enforcement_level`     | 必須ステータスチェックの実施がブランチで更新されるときにトリガーされます。                                                                          |
+| `update_strict_required_status_checks_policy`         | マージする前に最新にする必要があるブランチの要件が変更されるときにトリガーされます。                                                                     |
+| `rejected_ref_update`                                 | ブランチ更新の試行が拒否されるときにトリガーされます。                                                                                    |
+| `policy_override`                                     | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされるときにトリガーされます。{% ifversion fpt or ghes or ghae or ghec %}
+| `update_allow_force_pushes_enforcement_level`         | 保護されたブランチについて、フォースプッシュが有効化または無効化されるときにトリガーされます。                                                                |
+| `update_allow_deletions_enforcement_level`            | 保護されたブランチについて、ブランチ削除が有効化または無効化されるときにトリガーされます。                                                                  |
+| `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。                                                           |
+{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+
+### `pull_request`カテゴリのアクション
+
+| アクション                   | 説明                                                                            |
+| ----------------------- | ----------------------------------------------------------------------------- |
+| `create`                | Pull Requestが作成されたときにトリガーされます。                                                |
+| `close`                 | Pull Requestがマージされずにクローズされたときにトリガーされます。                                       |
+| `reopen`                | 以前クローズされたPull Requestが再オープンされたときにトリガーされます。                                    |
+| `マージ`                   | Pull Requestがマージされたときにトリガーされます。                                               |
+| `indirect_merge`        | Pull Requestのコミットがターゲットブランチにマージされたことで、そのPull Requestがマージされたと考えられるときにトリガーされます。 |
+| `ready_for_review`      | Pull Requestがレビューの準備ができたとしてマークされたときにトリガーされます。                                 |
+| `converted_to_draft`    | Pull Requestがドラフトに変換されたときにトリガーされます。                                           |
+| `create_review_request` | レビューが要求されたときにトリガーされます。                                                        |
+| `remove_review_request` | レビューの要求が削除されたときにトリガーされます。                                                     |
+
+### `pull_request_review`カテゴリのアクション
+
+| アクション    | 説明                        |
+| -------- | ------------------------- |
+| `サブミット`  | レビューがサブミットされたときにトリガーされます。 |
+| `却下`     | レビューが却下されたときにトリガーされます。    |
+| `delete` | レビューが削除されたときにトリガーされます。    |
+
+### `pull_request_review_comment`カテゴリのアクション
+
+| アクション    | 説明                         |
+| -------- | -------------------------- |
+| `create` | レビューコメントが追加されたときにトリガーされます。 |
+| `update` | レビューコメントが変更されたときにトリガーされます。 |
+| `delete` | レビューコメントが削除されたときにトリガーされます。 |
+
+{% endif %}
+
+### `repo` カテゴリアクション
+
+| アクション                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                               | ユーザが Organization 内のリポジトリの[可視性を変更](/github/administering-a-repository/setting-repository-visibility)するとトリガーされます。                                                                                                                                                                                                                                                                                                                                                                |
+| `actions_enabled`                      | リポジトリに対して {% data variables.product.prodname_actions %} が有効化されたときにトリガーされます。 UI を使用して表示できます。 REST API を使用して Audit log にアクセスする場合、このイベントは対象外です。 詳しい情報については、「[REST API を使用する](#using-the-rest-api)」を参照してください。                                                                                                                                                                                                                                                                       |
+| `add_member`                           | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                      |
+| `add_topic`                            | リポジトリ管理者がリポジトリに[トピックを追加](/articles/classifying-your-repository-with-topics)するとトリガーされます。{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_disabled`           | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にするとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。                                                                                                                                                                                                                                  |
+| `advanced_security_enabled`            | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を有効にするとトリガーされます。 詳しい情報については、「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %}
+| `archived`                             | リポジトリの管理者が[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% ifversion ghes %}
+| `config.disable_anonymous_git_access`  | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                                |
+| `config.enable_anonymous_git_access`   | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                                |
+| `config.lock_anonymous_git_access`     | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。                                                                                                                                                                                                                                                                                                           |
+| `config.unlock_anonymous_git_access`   | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %}
+| `create`                               | [新しいリポジトリが作成された](/articles/creating-a-new-repository)ときにトリガーされます。{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[リポジトリの暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。{% endif %}
+| `destroy`                              | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% ifversion fpt or ghec %}
+| `disable`                              | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %}
+| `enable`                               | リポジトリが再び有効になるときにトリガーされます。{% ifversion fpt or ghes or ghec %}
+| `remove_actions_secret`                | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。{% endif %}
+| `remove_member`                        | ユーザーが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                            |
+| `register_self_hosted_runner`          | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[リポジトリにセルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)」を参照してください。                                                                                                                                                                                                                                                                                        |
+| `remove_self_hosted_runner`            | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[リポジトリからランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)」を参照してください。                                                                                                                                                                                                                                                                                                      |
+| `remove_topic`                         | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `rename`                               | [リポジトリの名前が変更された](/articles/renaming-a-repository)ときにトリガーされます。{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`            | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                 |
+| `self_hosted_runner_offline`           | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`           | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %}
+| `set_actions_retention_limit`          | {% data variables.product.prodname_actions %}の成果物とログの保持期間が変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`         | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+| `移譲`                                   | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `transfer_start`                       | リポジトリの移譲が行われようとしているときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `unarchived`                           | リポジトリ管理者がリポジトリをアーカイブ解除するとトリガーされます。{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `repository_advisory` カテゴリアクション
+
+| アクション              | 説明                                                                                                                                                                                                    |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `close`            | ユーザがセキュリティアドバイザリをクローズするとトリガーされます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 |
+| `cve_request`      | ユーザがセキュリティアドバイザリのドラフトのために {% data variables.product.prodname_dotcom %} に CVE (Common Vulnerabilities and Exposures) 番号をリクエストするとトリガーされます。                                                              |
+| `github_broadcast` | {% data variables.product.prodname_dotcom %} が {% data variables.product.prodname_advisory_database %} でセキュリティアドバイザリを公開するとトリガーされます。                                                                 |
+| `github_withdraw`  | {% data variables.product.prodname_dotcom %} が誤って公開されたセキュリティアドバイザリを撤回するとトリガーされます。                                                                                                                     |
+| `オープン`             | ユーザがドラフトのセキュリティアドバイザリをオープンするとトリガーされます。                                                                                                                                                                |
+| `publish`          | ユーザがセキュリティアドバイザリを公開するとトリガーされます。                                                                                                                                                                       |
+| `reopen`           | ユーザがドラフトのセキュリティアドバイザリとして再オープンするとトリガーされます。                                                                                                                                                             |
+| `update`           | ユーザがドラフトまたは公開済みのセキュリティアドバイザリを編集するとトリガーされます。                                                                                                                                                           |
+
+### `repository_content_analysis`カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                            |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enable`  | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を有効にする](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 |
+| `disable` | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を無効にする](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 |
+
+{% endif %}{% ifversion fpt or ghec %}
+
+### `repository_dependency_graph` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                           |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% ifversion fpt or ghec %}プライベート{% endif %}リポジトリの依存関係グラフを無効にするとトリガーされます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 |
+| `enable`  | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% ifversion fpt or ghec %}プライベート{% endif %}リポジトリの依存関係グラフを有効にするとトリガーされます。                                                                                                                  |
+
+{% endif %}{% ifversion ghec or ghes or ghae %}
+### `repository_secret_scanning` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                                                |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository.                                                                                                      |
+
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+### `repository_vulnerability_alert` カテゴリアクション
+
+| アクション    | 説明                                                                                                                                                                                                                                                                                                                  |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 |
+| `却下`     | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency.                                                                                                                                |
+| `解決`     | リポジトリへの書き込みアクセスを持つユーザが変更をプッシュして、プロジェクトの依存関係の脆弱性を更新および解決するとトリガーされます。                                                                                                                                                                                                                                                 |
+
+{% endif %}{% ifversion fpt or ghec %}
+### `repository_vulnerability_alerts` カテゴリアクション
+
+| アクション                    | 説明                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `authorized_users_teams` | Organization のオーナーまたはリポジトリへの管理者権限を持つユーザが、リポジトリ内の脆弱性のある依存関係の {% data variables.product.prodname_dependabot_alerts %} を受け取ることを許可されたユーザまたは Team のリストを更新するとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 |
+| `disable`                | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を無効にするとトリガーされます。                                                                                                                                                                                                                                        |
+| `enable`                 | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を有効にするとトリガーされます。                                                                                                                                                                                                                                        |
+
+{% endif %}{% ifversion ghec %}
+### `role` category actions
+| アクション     | 説明                                                                                                                                                                                                                                                                                              |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`  | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."     |
+| `destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."          |
+| `update`  | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." |
+
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+### `secret_scanning` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                                   |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.                                                                                                      |
+
+### `secret_scanning_new_repos` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                                                                             |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.                                                                                                      |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `sponsors` カテゴリアクション
+
+| アクション                                         | 説明                                                                                                                                                                                                                                                                     |
+| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | カスタム金額を有効または無効にするとき、または提案されたカスタム金額を変更するときにトリガーされます (「[スポンサーシップ層を管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)」を参照)。                                                                                         |
+| `repo_funding_links_file_action`              | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                             |
+| `sponsor_sponsorship_cancel`                  | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                                           |
+| `sponsor_sponsorship_create`                  | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照)                                                                                                                         |
+| `sponsor_sponsorship_payment_complete`        | アカウントをスポンサーし、支払が処理されるとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照)                                                                                                                 |
+| `sponsor_sponsorship_preference_change`       | スポンサードアカウントからメールで最新情報を受け取るかどうかを変更するとトリガーされます (「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照)                                                                                                                           |
+| `sponsor_sponsorship_tier_change`             | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                   |
+| `sponsored_developer_approve`                 | {% data variables.product.prodname_sponsors %} アカウントが承認されるとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照）              |
+| `sponsored_developer_create`                  | {% data variables.product.prodname_sponsors %} アカウントが作成されるとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照）              |
+| `sponsored_developer_disable`                 | {% data variables.product.prodname_sponsors %} アカウントが無効になるとトリガーされます                                                                                                                                                                                                    |
+| `sponsored_developer_redraft`                 | {% data variables.product.prodname_sponsors %} アカウントが承認済みの状態からドラフト状態に戻るとトリガーされます                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | スポンサード Organization のプロフィールを編集するとトリガーされます（「[{% data variables.product.prodname_sponsors %} のプロフィール詳細を編集する](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照）                                             |
+| `sponsored_developer_request_approval`        | 承認のために {% data variables.product.prodname_sponsors %} のアプリケーションをサブミットするとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） |
+| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)」を参照)                                                                                                                         |
+| `sponsored_developer_update_newsletter_send`  | スポンサーにメールで最新情報を送信するとトリガーされます (「[スポンサーに連絡する](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)」を参照)                                                                                                                                    |
+| `waitlist_invite_sponsored_developer`         | 待ちリストから {% data variables.product.prodname_sponsors %} に参加するよう招待されたときにトリガーされます（「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照）  |
+| `waitlist_join`                               | スポンサード Organization になるために待ちリストに参加するとトリガーされます（「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照）                                   |
+{% endif %}
+
+### `team` カテゴリアクション
+
+| アクション                     | 説明                                                                                                                                                                                                                                                               |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member`              | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。                                                                                                                                                                    |
+| `add_repository`          | リポジトリの管理が Team に任せられるときにトリガーされます。                                                                                                                                                                                                                                |
+| `change_parent_team`      | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。                                                                                                                                                             |
+| `change_privacy`          | Team のプライバシー レベルが変更されるときにトリガーされます。                                                                                                                                                                                                                               |
+| `create`                  | 新たな Team が作成されるときにトリガーされます。                                                                                                                                                                                                                                      |
+| `demote_maintainer`       | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."  |
+| `destroy`                 | Team が Organization から削除されるときにトリガーされます。                                                                                                                                                                                                                          |
+| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." |
+| `remove_member`           | Organization のメンバーが[Team から削除される](/articles/removing-organization-members-from-a-team)ときにトリガーされます。                                                                                                                                                               |
+| `remove_repository`       | リポジトリが Team の管理下でなくなるときにトリガーされます。                                                                                                                                                                                                                                |
+
+### `team_discussions` カテゴリアクション
+
+| アクション     | 説明                                                                                                                                                                                     |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが Organization の Team ディスカッションを無効にするときにトリガーされます。 詳しい情報については [Organization の Team ディスカッションの無効化](/articles/disabling-team-discussions-for-your-organization)を参照してください。 |
+| `enable`  | Organization のオーナーが Organization の Team ディスカッションを有効にするときにトリガーされます。                                                                                                                     |
+
+{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### `workflows` カテゴリアクション
+
+{% data reusables.actions.actions-audit-events-workflow %}
+{% endif %}
+## 参考リンク
+
+- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
new file mode 100644
index 0000000000..b1a653c7a1
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -0,0 +1,31 @@
+---
+title: Organization のインストール済みインテグレーションをレビューする
+intro: Organization のインストール済みインテグレーションの権限レベルをレビューして、各インテグレーションの Organization リポジトリへのアクセス権を設定できます。
+redirect_from:
+  - /articles/reviewing-your-organization-s-installed-integrations
+  - /articles/reviewing-your-organizations-installed-integrations
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations
+  - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: インストールされたインテグレーションのレビュー
+---
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
+{% elsif ghae or ghes < 3.4 %}
+1. In the left sidebar, click **Installed {% data variables.product.prodname_github_apps %}**. ![Installed {% data variables.product.prodname_github_apps %} tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png)
+{% endif %}
+2. レビューする {% data variables.product.prodname_github_app %}の横にある [**Configure**] をクリックします。 ![[Configure] ボタン](/assets/images/help/organizations/configure-installed-integration-button.png)
+6. {% data variables.product.prodname_github_app %} の権限とリポジトリのアクセス権をレビューします。 ![{% data variables.product.prodname_github_app %} にすべてのリポジトリまたは特定のリポジトリへのアクセス権を付与するためのオプション](/assets/images/help/organizations/toggle-integration-repo-access.png)
+    - {% data variables.product.prodname_github_app %} に Organization のすべてのリポジトリへのアクセス権を付与するには、[**All repositories**] をクリックします。
+    - アプリケーションにアクセス権を付与する特定のリポジトリを選択するには、[**Only select repositories**] を選択し、続いてリポジトリ名を入力します。
+7. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
new file mode 100644
index 0000000000..df495a0d4f
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -0,0 +1,17 @@
+---
+title: Managing two-factor authentication for your organization
+shortTitle: Manage 2FA
+intro: You can view whether users with access to your organization have two-factor authentication (2FA) enabled and require 2FA.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /preparing-to-require-two-factor-authentication-in-your-organization
+  - /requiring-two-factor-authentication-in-your-organization
+---
+
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..691fe68198
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: Organization で 2 要素認証の義務化を準備する
+intro: 2 要素認証を義務化する前に、予定されている変更についてユーザに通知し、どのユーザーが 2 要素認証をすでに使用しているかを確認することができます。
+redirect_from:
+  - /articles/preparing-to-require-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 2FAを必須とする準備
+---
+
+Organization で 2 要素認証を義務付ける 1 週間以上前に、{% ifversion fpt or ghec %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーと外部コラボレーター{% endif %}に通知することをおすすめします。
+
+Organization で 2 要素認証を必須にすると、2 要素認証を使わないメンバー、外部コラボレーター、および支払いマネージャー (ボットアカウントを含む) は Organization から削除され、そのリポジトリにアクセスできなくなります。 Organization のプライベートリポジトリのフォークへのアクセスも失います。
+
+組織で 2 要素認証を必須にする前に、次の準備をすることをおすすめします:
+  - 個人アカウントで [2 要素認証を有効化する](/articles/securing-your-account-with-two-factor-authentication-2fa/)
+  - Organization のユーザに、自分のアカウントで 2 要素認証をセットアップするよう指示する
+  - [Organization でどのユーザが 2 要素認証を有効にしているか](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/)を確認する
+  - 2 要素認証が有効になると、2 要素認証を使っていないユーザは自動的に Organization から削除されることを告知する
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..91e700330f
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Organization で 2 要素認証を要求する
+intro: 'Organization のオーナーは、 {% ifversion fpt or ghec %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバー、外部のコラボレーター{% endif %}に、それぞれの個人アカウントに対する 2 要素認証を有効にするように義務付けることで、悪意のある行為者が Organization のリポジトリや設定にアクセスしにくくすることができます。'
+redirect_from:
+  - /articles/requiring-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Require 2FA
+---
+
+## Organization の2 要素認証について
+
+{% data reusables.two_fa.about-2fa %} Organization のすべての{% ifversion fpt or ghec %}メンバー、外部コラボレーター、支払いマネージャー{% else %}メンバーおよび外部コラボレーター{% endif %}に、{% data variables.product.product_name %} で 2 要素認証を有効にすることを義務付けることができます。 2 要素認証の詳細は「[2 要素認証 (2FA) でアカウントを保護する](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。
+
+{% ifversion fpt or ghec %}
+
+Enterprise で Organization の 2 要素認証を必須にすることもできます。 詳しい情報については、「[Enterprise にセキュリティ設定のポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)」以下を参照してください。
+
+{% endif %}
+
+{% warning %}
+
+**警告:**
+
+- Organization に対して 2 要素認証の使用を義務付ける場合、2FA を使用しない{% ifversion fpt or ghec %}メンバー、外部コラボレーター、支払いマネージャー {% else %}メンバー、外部コラボレーター{% endif %} (ボット アカウントを含む) は Organization から削除され、そのリポジトリへのアクセス権が失われます。 Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization から削除されてから 3 か月以内に、個人アカウントに対して 2 要素認証を有効にすれば、[それらのアカウントが持っていたアクセス特権と設定を復元](/articles/reinstating-a-former-member-of-your-organization)できます。
+- 義務付けられた 2 要素認証を有効にした後に、Organization のオーナー、メンバー、{% ifversion fpt or ghec %}支払いマネージャー、{% endif %} または外部コラボレーターがそれぞれの個人アカウントで 2 要素認証を無効にすると、それらは Organization から自動的に削除されます。
+- あなたが、2 要素認証を義務付けている Organization の唯一のオーナーである場合、その Organization での 2 要素認証義務を無効にしなければ、あなたの個人アカウントの 2 要素認証を無効にすることはできません。
+
+{% endwarning %}
+
+{% data reusables.two_fa.auth_methods_2fa %}
+
+## 必要な環境
+
+{% ifversion fpt or ghec %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーおよび外部コラボレーター{% endif %}に、 2 要素認証を使用することを義務付けるには、まず{% data variables.product.product_name %} の自分自身の個人アカウントで 2 要素認証を有効にする必要があります。 詳細は「[2 要素認証 (2FA) でアカウントを保護する](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。
+
+2 要素認証の使用を義務付ける前に、{% ifversion fpt or ghec %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバー、外部コラボレーター{% endif %}に通知して、それぞれのアカウントで 2 要素認証をセットアップするように依頼することをおすすめします。 メンバーと外部のコラボレーターがすでに 2 要素認証を使用しているかどうかを確認できます。 詳細は「[Organization 内のユーザが 2 要素認証を有効にしているか確認する](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)」を参照してください。
+
+## Organization で 2 要素認証を要求する
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+{% ifversion fpt or ghec %}
+8. Organization から削除されるメンバーまたは外部コラボレーターが存在する場合、彼らに招待状を送信して、元の権限と Organization へのアクセス権を復元できるようにすることをおすすめします。 招待を受諾できるためには、まず 2 要素認証が有効でなければなりません。
+{% endif %}
+
+## Organization から削除された人々を表示する
+
+2 要素認証義務に従っていないために Organization から自動的に削除された人々を表示するには、Organization から削除された人々を対象に、[Organization の Audit log を検索する](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)ことができます。 Audit log イベントでは、削除された理由が 2 要素認証義務に従わなかったことなのかどうかが示されます。
+
+![2 要素認証の違反により削除されたユーザーを示す Audit log イベント](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+4. 検索クエリを入力します。 以下のように検索します:
+    - 削除された Organization のメンバーを検索するには、検索クエリで `action:org.remove_member` を使用します
+    - 削除された外部コラボレーターを検索するには、検索クエリで `action:org.remove_outside_collaborator` を使用します{% ifversion fpt or ghec %}
+    - 削除された支払いマネージャーを検索するには、検索クエリで `action:org.remove_billing_manager` を使用します{% endif %}
+
+ また、検索で[時間枠](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action)を使用すれば、Organization から削除された人々を表示できます。
+
+## 削除されたメンバーと外部コラボレーターを Organization に復帰できるようにする
+
+2要素認証の利用の要求を有効化したときにOrganizationから削除されたメンバーあるいは外部のコラボレータがいれば、その人たちには削除されたことを知らせるメールが届きます。 そうなった場合には、彼らは個人アカウントで2FAを有効化し、OrganizationのオーナーにOrganizationへのアクセスを求めなければなりません。
+
+## 参考リンク
+
+- 「[Organization 内のユーザーが 2 要素認証を有効にしているかどうかを表示する](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)」
+- 「[2 要素認証でアカウントを保護する](/articles/securing-your-account-with-two-factor-authentication-2fa)」
+- "[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)"
+- "[以前の外部コラボレーターの Organization へのアクセス権を回復する](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
new file mode 100644
index 0000000000..f704b620f3
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -0,0 +1,33 @@
+---
+title: Organization 内のユーザが 2 要素認証を有効にしているかどうかを表示する
+intro: どの Organization のオーナー、メンバー、および 外部コラボレーターが 2 要素認証を有効にしているかを確認できます。
+redirect_from:
+  - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View 2FA usage
+---
+
+{% note %}
+
+**メモ:** {% ifversion fpt or ghec %}オーナー、支払いマネージャーおよび{% else %}{% endif %}外部コラボレーターを含むすべてのメンバーに、2 要素認証を有効にするよう要求できます。 詳しい情報については [Organization で 2 要素認証を要求する](/articles/requiring-two-factor-authentication-in-your-organization)を参照してください。
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. Organization のオーナー含め、2 要素認証を有効または無効にした Organization メンバーを表示するには、[**2FA**] をクリックして、[**Enabled**] または [**Disabled**] を選択します。 ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png)
+5. Organization の外部コラボレーターを表示するには、[People] タブの下の [**Outside collaborators**] をクリックします。 ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png)
+6. どの外部コラボレーターが 2 要素認証を有効または無効にしているかを確認するには、右側の [**2FA**] をクリックして、[**Enabled**] または [**Disabled**] を選択します。 ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
+
+## 参考リンク
+
+- 「[Organization における人のロールを表示する](/articles/viewing-people-s-roles-in-an-organization)」
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index ab0472104a..b1db1c53d8 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -40,8 +40,8 @@ To further support your team's collaboration abilities, you can upgrade to {% da
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. 検索フィールドで、招待する人の名前を入力し、一致するリストの名前をクリックします。 ![リポジトリに招待する人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. [Choose a role] で、人に付与する権限を選択し、[**Add NAME to REPOSITORY**] をクリックします。 ![人の権限を選択する](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index dfe4d51372..e09da8331d 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -28,9 +28,13 @@ Organization のリポジトリからコラボレーターを削除すると、
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![リポジトリに招待する Team または人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png)
+1. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![リポジトリに招待する Team または人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. ![Team または人の権限を選択する](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
 ## Organization のリポジトリへの個人のアクセスを管理する
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 2c0dc2bc92..36fa4a53a6 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -78,6 +78,10 @@ You can configure this behavior for an organization using the procedure below. 
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+{% ifversion ghec or ghae or ghes %}If a policy is disabled for an enterprise, it cannot be enabled for organizations.{% endif %} If a policy is disabled for an organization, it cannot be enabled for repositories. If an organization enables a policy, the policy can be disabled for individual repositories.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 ### Organization のプライベートフォークポリシーを設定する
 
 {% data reusables.profile.access_org %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index e2c500edbb..4828e7df7c 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -24,10 +24,13 @@ Organization 内にあるリポジトリのプロジェクトボードを無効
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-4. Organization 全体のプロジェクトボードを無効化するのか、Organization 内にあるリポジトリのプロジェクトボードを無効化するのか、その両方なのかを判断します。 次に [Projects] の下で:
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+{% endif %}
+1. Organization 全体のプロジェクトボードを無効化するのか、Organization 内にあるリポジトリのプロジェクトボードを無効化するのか、その両方なのかを判断します。 次に [Projects] の下で:
     - Organization 全体のプロジェクトボードを無効化するには、[**Enable projects for the organization**] の選択を解除します。
     - Organization 内にあるリポジトリのプロジェクトボードを無効化するには、[**Enable projects for all repositories**] の選択を解除します。 ![Organization や Organization の全リポジトリのプロジェクトを無効にするチェックボックス](/assets/images/help/projects/disable-org-projects-checkbox.png)
-5. [**Save**] をクリックします。
+1. [**Save**] をクリックします。
 
 {% data reusables.organizations.disable_project_board_results %}
 
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index 779adc79f7..51760f93a9 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -10,14 +10,21 @@ versions:
 shortTitle: Jiraの統合
 ---
 
+{% ifversion ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![左サイドバーの [OAuth applications] タブ](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. [**New OAuth App**] をクリックします。
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.user_settings.access_settings %}
-2. 左サイドバーの [**Organization settings**] で、Organization の名前をクリックします。 ![サイドバーの Organization 名](/assets/images/help/settings/organization-settings-from-sidebar.png)
-3. 左サイドバーの **[Developer settings]** で、[**OAuth applications**] をクリックします。 ![左サイドバーの [OAuth applications] タブ](/assets/images/help/organizations/org-oauth-applications-ghe.png)
-4. [**Register a new application**] をクリックします。
-5. [**Application name**] に "Jira" と入力します。
-6. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。
-7. [**Authorization callback URL**] に、JIRA インスタンスの完全な URL を入力します。
-8. **Register application** をクリックする。 ![[Register application] ボタン](/assets/images/help/oauth/register-application-button.png)
+1. 左サイドバーの [**Organization settings**] で、Organization の名前をクリックします。 ![サイドバーの Organization 名](/assets/images/help/settings/organization-settings-from-sidebar.png)
+1. 左サイドバーの **[Developer settings]** で、[**OAuth applications**] をクリックします。 ![左サイドバーの [OAuth applications] タブ](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. [**Register a new application**] をクリックします。
+{% endif %}
+1. [**Application name**] に "Jira" と入力します。
+2. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。
+3. [**Authorization callback URL**] に、JIRA インスタンスの完全な URL を入力します。
+4. **Register application** をクリックする。 ![[Register application] ボタン](/assets/images/help/oauth/register-application-button.png)
 9. [**Organization owned applications**] で、[Client ID] と [Client Secret] の値を確認します。 ![クライアント ID とクライアントシークレット](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index 28c8ade287..c6181de0dc 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -24,14 +24,13 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.slack-channel %}
 {% data reusables.reminders.days-dropdown %}
 {% data reusables.reminders.times-dropdowns %}
 {% data reusables.reminders.tracked-repos %}
-11. [Filter by team assigned to review code] で、[**Add a team**] ドロップダウンをクリックし、1 つ以上の Team を選択します。 最大 100 チームまで追加できます。 選択した Team が、上で選択する [Tracked repositories] にアクセスできない場合は、スケジュールされたリマインダーは作成できません。 ![[Add a team] ドロップダウン](/assets/images/help/organizations/scheduled-reminders-add-teams.png)
+1.  [Filter by team assigned to review code] で、[**Add a team**] ドロップダウンをクリックし、1 つ以上の Team を選択します。 最大 100 チームまで追加できます。 選択した Team が、上で選択する [Tracked repositories] にアクセスできない場合は、スケジュールされたリマインダーは作成できません。 ![[Add a team] ドロップダウン](/assets/images/help/organizations/scheduled-reminders-add-teams.png)
 {% data reusables.reminders.ignore-drafts %}
 {% data reusables.reminders.no-review-requests %}
 {% data reusables.reminders.author-reviews %}
@@ -47,7 +46,6 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
@@ -56,7 +54,6 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 4871c24f30..9b3aec732a 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -23,6 +23,7 @@ Organization レベルでプライベート{% ifversion ghes or ghec or ghae %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index 150595a966..8ed94571a8 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -63,3 +63,7 @@ Organization のオーナーの Team のメンバーは、人に*支払いマネ
 {% data reusables.organizations.billing-settings %}
 1. [Billing management] で、[Billing managers] の右の [**Add**] をクリックします。 ![支払いマネージャーの招待](/assets/images/help/billing/settings_billing_managers_list.png)
 6. 追加したい人のユーザ名あるいはメールアドレスを入力し、[**Send Invitation**] をクリックします。 ![支払いマネージャーの招待ページ](/assets/images/help/billing/billing_manager_invite.png)
+
+## 参考リンク
+
+- "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index 571030bf90..ad06e53fb4 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -90,6 +90,8 @@ You can only choose an additional permission if it's not already included in the
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
 - **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts.
+- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}.
+- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}.
 - **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts.
 
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 3e5ec14950..20cb8fa8e6 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -31,24 +31,11 @@ Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for
 
 ## Okta で {% data variables.product.prodname_ghe_cloud %} アプリケーションを追加する
 
-{% data reusables.saml.okta-sign-into-your-account %}
-1. Navigate to the [Github Enterprise Cloud - Organization](https://www.okta.com/integrations/github-enterprise-cloud-organization) application in the Okta Integration Network and click **Add Integration**.
-1. オプションで、[Application label] の右にアプリケーションのわかりやすい名前を入力します。
-1. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. たとえば、Organization の URL が https://github.com/octo-org の場合、Organization 名は `octo-org` となります。
-1. [**Done**] をクリックします。
-
-## SAML SSO の有効化とテスト
-
-{% data reusables.saml.okta-sign-into-your-account %}
-{% data reusables.saml.okta-dashboard-click-applications %}
-{% data reusables.saml.okta-applications-click-ghec-application-label %}
-{% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
 1. SAML 2.0 の設定方法に関するガイドから、サインオン URL、発行者 URL、公開の証明書を使用して、{% data variables.product.prodname_dotcom %} での SAML SSO を有効化してテストします。 詳細は「[Organization での SAML シングルサインオンの有効化とテスト](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。
 
 ## Okta で SCIM を使ってアクセスのプロビジョニングを設定する
-
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.okta-provisioning-tab %}
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index c1dd341421..c8df8f0db8 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -57,7 +57,11 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
 1. Select **Only notify requested team members.** ![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
 1. [**Save changes**] をクリックします。
 {% endif %}
@@ -67,7 +71,11 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
 1. [**Enable auto assignment**] を選択します。 ![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
 1. [How many team members should be assigned to review?] でドロップダウンメニューを使用し、各プルリクエストに割り当てるレビュー担当者の数を選択します。 ![[Number of reviewers] ドロップダウン](/assets/images/help/teams/review-assignment-number.png)
 1. [Routing algorithm] のドロップダウンメニューで、使用するアルゴリズムを選択します。 詳細は、「[ルーティングアルゴリズム](#routing-algorithms)」を参照してください。 ![[Routing algorithm] ドロップダウン](/assets/images/help/teams/review-assignment-algorithm.png)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
index 9fa42d6563..7e2203682f 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
@@ -27,7 +27,6 @@ shortTitle: スケジュールされたリマインダー
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.slack-channel %}
@@ -51,7 +50,6 @@ shortTitle: スケジュールされたリマインダー
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.edit-existing %}
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
@@ -62,7 +60,6 @@ shortTitle: スケジュールされたリマインダー
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![[Scheduled reminders] ボタン](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.delete %}
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index 148f2ed2cd..7d67ccd3d6 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -176,7 +176,7 @@ To review who can delete a package version, see "[Required permissions to delete
 - 削除後30日以内にパッケージを復元する。
 - 同一のパッケージ名前空間がまだ使用可能であり、新しいパッケージで再使用されていない。
 
-たとえば、リポジトリ`octo-repo-owner/octo-repo`のスコープが付いていた、`octo-package`という名前のrubygemパッケージを削除した場合、パッケージ名前空間`rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` がまだ使用可能で、かつ30日間が経過していない場合にのみ、そのパッケージを復元できます。
+For example, if you have a deleted RubyGems package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
 
 {% ifversion fpt or ghec %}
 To restore a deleted package, you must also meet one of these permission requirements:
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
index 22d46ba47a..d801f5049b 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -23,7 +23,7 @@ shortTitle: RubyGems registry
 
 ## Prerequisites
 
-- You must have rubygems 2.4.1 or higher. To find your rubygems version:
+- You must have RubyGems 2.4.1 or higher. To find your RubyGems version:
 
   ```shell
   $ gem --version
@@ -86,7 +86,7 @@ If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this exa
 
 ```
 
-To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
 
 ```shell
 $ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index b9b270b992..fc37d655fb 100644
--- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -23,7 +23,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
 ## Verifying a domain for your user site
 
 {% data reusables.user_settings.access_settings %}
-1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
@@ -37,7 +37,7 @@ Organization owners can verify custom domains for their organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
diff --git a/translations/ja-JP/content/pages/quickstart.md b/translations/ja-JP/content/pages/quickstart.md
index 4d164aef7c..5fd2d42e5c 100644
--- a/translations/ja-JP/content/pages/quickstart.md
+++ b/translations/ja-JP/content/pages/quickstart.md
@@ -25,12 +25,12 @@ This guide will lead you through creating a user site at `username.github.io`.
 {% data reusables.repositories.create_new %}
 1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`. ![Repository name field](/assets/images/help/pages/create-repository-name-pages.png)
 {% data reusables.repositories.sidebar-settings %}
-1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![左のサイドバーのPageタブ](/assets/images/help/pages/pages-tab.png)
+{% data reusables.pages.sidebar-pages %}
 1. Click **Choose a theme**. ![[Choose a theme] ボタン](/assets/images/help/pages/choose-theme.png)
-1. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png)
-1. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
-1. When you are done editing the file, click **Commit changes**.
-1. Visit `username.github.io` to view your new website. **メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。
+2. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png)
+3. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
+4. When you are done editing the file, click **Commit changes**.
+5. Visit `username.github.io` to view your new website. **メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。
 
 ## Changing the title and description
 
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index 2510f9339c..668f9175c0 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -35,7 +35,7 @@ topics:
 
 _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
 
-Organization オーナー、およびリポジトリにプッシュアクセスを持つユーザは、{% data variables.product.product_name %} の API でチェックおよびステータスを作成できます。 詳しい情報については、「[チェック](/rest/reference/checks)」および「[ ステータス](/rest/reference/repos#statuses)」を参照してください。
+Organization オーナー、およびリポジトリにプッシュアクセスを持つユーザは、{% data variables.product.product_name %} の API でチェックおよびステータスを作成できます。 詳しい情報については、「[チェック](/rest/reference/checks)」および「[ ステータス](/rest/reference/commits#commit-statuses)」を参照してください。
 
 ## チェック
 
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index 20dd070b28..886696d05c 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -162,6 +162,7 @@ For more information on creating pull requests in {% data variables.product.prod
 ## 参考リンク
 
 - [フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)"
 - [プルリクエストのベースブランチを変更する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)
 - 「[サイドバーからプロジェクトボードへ Issue およびプルリクエストを追加する](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)」
 - 「[クエリパラメータによる Issue およびプルリクエストの自動化について](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)」
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 5e291dc4d3..9f51501b0b 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -22,6 +22,7 @@ children:
   - /using-query-parameters-to-create-a-pull-request
   - /changing-the-stage-of-a-pull-request
   - /requesting-a-pull-request-review
+  - /keeping-your-pull-request-in-sync-with-the-base-branch
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
 shortTitle: Propose changes
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
new file mode 100644
index 0000000000..6c3221dd88
--- /dev/null
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
@@ -0,0 +1,53 @@
+---
+title: Keeping your pull request in sync with the base branch
+intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.'
+permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Update the head branch
+---
+
+## About keeping your pull request in sync
+
+Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging.
+
+You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true:
+
+* There are no merge conflicts between the pull request branch and the base branch.
+* The pull request branch is not up to date with the base branch.
+* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} or the setting to always suggest updating branches is enabled{% endif %}.
+
+For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}" and "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}."
+
+If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)."
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created.
+{% else %}
+Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request.
+{% endif %}
+
+## Updating your pull request branch
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull requests" list, click the pull request you'd like to update.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+1. In the merge section near the bottom of the page, you can:
+   - Click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png)
+   - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch. ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png)
+{% else %}
+1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch.png)
+{% endif %}
+
+## 参考リンク
+
+- [プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)"
+- [フォークから作成されたプルリクエストブランチへの変更のコミット](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
index 2f6df0b320..5a9dd85706 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
@@ -19,4 +19,4 @@ shortTitle: Configure commit rebasing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. [Merge button] の下で [**Allow rebase merging**] を選択します。 これにより、コントリビューターが個々のコミットをベースブランチにリベースすることでプルリクエストをマージできるようになります。 ここで他のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![プルリクエストのリベースコミット](/assets/images/help/repository/pr-merge-rebase.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. これにより、コントリビューターが個々のコミットをベースブランチにリベースすることでプルリクエストをマージできるようになります。 ここで他のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![プルリクエストのリベースコミット](/assets/images/help/repository/pr-merge-rebase.png)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index 05f0e564aa..8ea9604354 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -21,8 +21,8 @@ shortTitle: Configure commit squashing
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 必要であれば、[Merge button] の下の [**Allow merge commits**] を選択します。 これにより、コントリビューターがコミットの全ての履歴と共にプルリクエストをマージできるようになります。 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. [Merge button] の下にある [**Allow squash merging**] を選択します。 これにより、コントリビューターが全てのコミットを 1 つのコミットに squash してプルリクエストをマージできるようになります。 [**Allow squash merging**] 以外のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![プルリクエストの squash したコミット](/assets/images/help/repository/pr-merge-squash.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. これにより、コントリビューターがコミットの全ての履歴と共にプルリクエストをマージできるようになります。 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
+4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. これにより、コントリビューターが全てのコミットを 1 つのコミットに squash してプルリクエストをマージできるようになります。 [**Allow squash merging**] 以外のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![プルリクエストの squash したコミット](/assets/images/help/repository/pr-merge-squash.png)
 
 ## 参考リンク
 
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
index 9ee6121904..64c9ddcb06 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -16,6 +16,7 @@ children:
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
   - /using-a-merge-queue
+  - /managing-suggestions-to-update-pull-request-branches
   - /managing-auto-merge-for-pull-requests-in-your-repository
   - /managing-the-automatic-deletion-of-branches
 shortTitle: Configure PR merges
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 5ce2614d15..95abb38e4f 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -26,4 +26,4 @@ shortTitle: Manage auto merge
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. [Merge button] の下にある [**Allow auto-merge**] を選択または選択解除します。 ![自動マージを許可または禁止するチェックボックス](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
+1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**. ![自動マージを許可または禁止するチェックボックス](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
new file mode 100644
index 0000000000..a724a1302b
--- /dev/null
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -0,0 +1,23 @@
+---
+title: Managing suggestions to update pull request branches
+intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+versions:
+  fpt: '*'
+  ghes: '> 3.4'
+  ghae: issue-6069
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage branch updates
+permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
+---
+
+## About suggestions to update a pull request branch
+
+If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+## Managing suggestions to update a pull request branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**. ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
index 2e3a2e08ab..d36335c6e3 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
@@ -19,7 +19,7 @@ shortTitle: Automatic branch deletion
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. [Merge button] の下で [**Automatically delete head branches**] を選択または選択解除します。 ![ブランチの自動的削除を有効化または無効化するチェックボックス](/assets/images/help/repository/automatically-delete-branches.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or unselect **Automatically delete head branches**. ![ブランチの自動的削除を有効化または無効化するチェックボックス](/assets/images/help/repository/automatically-delete-branches.png)
 
 ## 参考リンク
 - [プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 6339d4af2c..96a356dc63 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -84,7 +84,7 @@ remote: error: Changes have been requested.
 
 必須ステータスチェックにより、コラボレータが保護されたブランチに変更を加える前に、すべての必須 CI テストにパスしていることが保証されます。 詳細は「[保護されたブランチを設定する](/articles/configuring-protected-branches/)」および「[必須ステータスチェックを有効にする](/articles/enabling-required-status-checks)」を参照してください。 詳しい情報については、「[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)」を参照してください。
 
-ステータスチェック必須を有効にする前に、ステータス API を使用するようにリポジトリを設定する必要があります。 詳しい情報については、REST ドキュメントの「[リポジトリ](/rest/reference/repos#statuses)」を参照してください。
+ステータスチェック必須を有効にする前に、ステータス API を使用するようにリポジトリを設定する必要があります。 詳しい情報については、REST ドキュメントの「[リポジトリ](/rest/reference/commits#commit-statuses)」を参照してください。
 
 ステータスチェック必須を有効にすると、すべてのステータスチェック必須がパスしないと、コラボレータは保護されたブランチにマージできません。 必須ステータスチェックをパスしたら、コミットを別のブランチにプッシュしてから、マージするか、保護されたブランチに直接プッシュする必要があります。
 
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index e2ac666df2..e0685d1a5f 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -52,7 +52,8 @@ Prerequisites for repository transfers:
   $ git remote set-url origin <em>新しい URL</em>
   ```
 
-- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
+- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
 詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 54e3a371fa..590ab247ae 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -51,6 +51,8 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to
 CODEOWNERS ファイルは、[一部の例外](#syntax-exceptions)を除いて、[gitignore](https://git-scm.com/docs/gitignore#_pattern_format) ファイルで使用されるルールのほとんどに従うパターンを使用します。 パターンの後には1つ以上の{% data variables.product.prodname_dotcom %}のユーザー名あるいはTeam名が続きます。これらの名前には標準の`@username`あるいは`@org/team-name`フォーマットが使われます。 Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
 
 CODEOWNERS ファイルのいずれかの行に無効な構文が含まれている場合、そのファイルは検出されず、レビューのリクエストには使用されません。
+
+CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 ### CODEOWNERS ファイルの例
 ```
 # これはコメントです。
@@ -98,6 +100,10 @@ apps/ @octocat
 # ファイルを所有しています。
 /docs/ @doctocat
 
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
 # In this example, @octocat owns any file in the `/apps` 
 # directory in the root of your repository except for the `/apps/github` 
 # subdirectory, as its owners are left empty.
@@ -113,21 +119,6 @@ gitignore ファイルには、CODEOWNERS ファイルでは動作しないい
 ## CODEOWNERS and branch protection
 Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)」を参照してください。
 
-### CODEOWNERS ファイルの例
-```
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat.
-/apps/ @doctocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat or @octocat.
-/apps/ @doctocat @octocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from a member of the @example-org/content team.
-/apps/ @example-org/content-team
-```
-
 
 ## 参考リンク
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 37f6dba576..b978d9f1ca 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -87,6 +87,10 @@ You can configure this behavior for a repository using the procedure below. Modi
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 ### リポジトリのプライベートフォークポリシーを設定する
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -137,11 +141,11 @@ You can configure whether {% if internal-actions%}actions and {% endif %}workflo
 
 ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
 
-リポジトリ内の {% data variables.product.prodname_actions %} アーティファクトとログの保持期間を設定できます。
+You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-ワークフローによって作成された特定のアーティファクトのカスタム保存期間を定義することもできます。 詳しい情報については、「[アーティファクトの保持期間を設定する](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)」を参照してください。
+You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
 
 ## リポジトリの保持期間を設定する
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index f3a1e674f5..ff1afb0b17 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -22,8 +22,12 @@ Anyone with admin permissions to a repository can configure autolink references
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 左のサイドバーで、[**Autolink references**] をクリックします。 ![左サイドバーの [Autolink references] タブ](/assets/images/help/repository/autolink-references-tab.png)
-4. [**Add autolink reference**] をクリックします。 ![自動リンクの参照情報を入力するボタン](/assets/images/help/repository/add-autolink-reference-details.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
+{% else %}
+1. 左のサイドバーで、[**Autolink references**] をクリックします。 ![左サイドバーの [Autolink references] タブ](/assets/images/help/repository/autolink-references-tab.png)
+{% endif %}
+1. [**Add autolink reference**] をクリックします。 ![自動リンクの参照情報を入力するボタン](/assets/images/help/repository/add-autolink-reference-details.png)
 5. [Reference prefix] に、コラボレータ が外部リソースへの自動リンクを生成する際に使用する短くわかりやすいプレフィックスを入力します。 ![外部システムの略語を入力するフィールド](/assets/images/help/repository/add-reference-prefix-field.png)
 6. [Target URL] に、リンク先の外部システムへのリンクを入力します。 参照番号の変数は`<num>`のままにしてください。 ![外部システムへのURLを入力するフィールド](/assets/images/help/repository/add-target-url-field.png)
 7. [**Add autolink reference**] をクリックします。 ![自動リンクの参照を追加するボタン](/assets/images/help/repository/add-autolink-reference.png)
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
index e26514a92b..a092f0b3a6 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
@@ -28,7 +28,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. [Manage access] の検索フィールドで、検索する Team または人の名前を入力します。 ![アクセスできる Team または人のリストをフィルタリングするための検索フィールド](/assets/images/help/repository/manage-access-filter.png)
 
 ## Team または人の権限を変更する
@@ -42,7 +42,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. 検索フィールドで、招待する Team または人の名前を入力し、リストから一致する名前をクリックします。 ![リポジトリに招待する Team または人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**. ![Team または人の権限を選択する](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
@@ -51,7 +51,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. [Manage access] でアクセスを削除する Team またはユーザーを探し、{% octicon "trash" aria-label="The trash icon" %} をクリックします。 ![アクセス削除用のゴミ箱アイコン](/assets/images/help/repository/manage-access-remove.png)
 
 ## 参考リンク
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/index.md b/translations/ja-JP/content/repositories/working-with-files/using-files/index.md
index e206e20283..8fd80fa5d2 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/index.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/index.md
@@ -8,7 +8,7 @@ versions:
   ghec: '*'
 children:
   - /navigating-code-on-github
-  - /tracking-changes-in-a-file
+  - /viewing-a-file
   - /getting-permanent-links-to-files
   - /working-with-non-code-files
 ---
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md
new file mode 100644
index 0000000000..352bb0c37b
--- /dev/null
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -0,0 +1,49 @@
+---
+title: Viewing a file
+intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+redirect_from:
+  - /articles/using-git-blame-to-trace-changes-in-a-file
+  - /articles/tracing-changes-in-a-file
+  - /articles/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file
+  - /repositories/working-with-files/using-files/tracking-changes-in-a-file
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View files and track file changes
+---
+
+## Viewing or copying the raw file content
+
+With the raw view, you can view or copy the raw content of a file without any styling.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Click the file that you want to view.
+2. In the upper-right corner of the file view, click **Raw**. ![Screenshot of the Raw button in the file header](/assets/images/help/repository/raw-file-button.png)
+3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+
+## Viewing the line-by-line revision history for a file
+
+Blame ビューでは、{% octicon "versions" aria-label="The prior blame icon" %} をクリックすることで、ファイル全体の行ごとのリビジョン履歴やファイル内の 1 つの行のリビジョン履歴を表示することができます。 {% octicon "versions" aria-label="The prior blame icon" %} をクリックするたびに、変更をコミットした者と時間を含む、その行の過去のリビジョン情報が表示されます。
+
+![Git blame ビュー](/assets/images/help/repository/git_blame.png)
+
+ファイルやプルリクエストでは、{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} メニューを使って、選択した行や行の範囲の Git blame を表示することもできます。
+
+![選択した行の Git blame を表示するオプションのあるケバブメニュー](/assets/images/help/repository/view-git-blame-specific-line.png)
+
+{% tip %}
+
+**ヒント:** コマンドライン上で、ファイル内の行のリビジョン履歴を表示するために `git blame` を使うこともできます。 詳細は [Git の `git blame` のドキュメンテーション](https://git-scm.com/docs/git-blame)を参照してください。
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. クリックして、表示したい行の履歴のファイルを開きます。
+3. ファイルビューの右上隅で [**Blame**] をクリックして blame ビューを開きます。 ![[Blame] ボタン](/assets/images/help/repository/blame-button.png)
+4. 特定の行の過去のリビジョンを表示するには、見てみたい変更が見つかるまで {% octicon "versions" aria-label="The prior blame icon" %} をクリックします。 ![さらに前の状態に遡るボタン](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 618c10379b..a72acf5017 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -116,7 +116,7 @@ STLファイルを含むコミットあるいは一連の変更を見る場合
 <script src="https://embed.github.com/view/3d/<username>/<repo>/<ref>/<path_to_file>"></script>
 ```
 
-たとえばモデルのURLが[github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl)なら、埋め込むコードは以下のようになるでしょう。
+For example, if your model's URL is [`github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl`](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl), your embed code would be:
 
 ```html
 <script src="https://embed.github.com/view/3d/skalnik/secret-bear-clip/master/stl/clip.stl"></script>
diff --git a/translations/ja-JP/content/rest/guides/building-a-ci-server.md b/translations/ja-JP/content/rest/guides/building-a-ci-server.md
index 52e65e9a5e..00f2189119 100644
--- a/translations/ja-JP/content/rest/guides/building-a-ci-server.md
+++ b/translations/ja-JP/content/rest/guides/building-a-ci-server.md
@@ -132,7 +132,7 @@ GitHubでは長年、CIを管理するため[Janky][janky]の特定のバージ
 
 これら全ての通信は、チャットルームに集約されます。 この例を使用するために、独自のCI設定を構築する必要はありません。 いつでも[GitHubインテグレーション][integrations]に頼ることができます。
 
-[status API]: /rest/reference/repos#statuses
+[status API]: /rest/reference/commits#commit-statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
diff --git a/translations/ja-JP/content/rest/guides/delivering-deployments.md b/translations/ja-JP/content/rest/guides/delivering-deployments.md
index 24700538d6..4f00fc39ba 100644
--- a/translations/ja-JP/content/rest/guides/delivering-deployments.md
+++ b/translations/ja-JP/content/rest/guides/delivering-deployments.md
@@ -20,7 +20,7 @@ topics:
 
 このAPIでは、ステータスAPIを使って、利用できる設定を示します。 このシナリオでは、以下を行います。
 
-* ププルリクエストをマージします。
+* Merge a pull request.
 * CIが終了したら、それに応じてプルリクエストのステータスを設定します。
 * プルリクエストがマージされたら、サーバーでデプロイメントを実行します。
 
diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
index 5211485efa..bc3943fa8b 100644
--- a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
@@ -390,7 +390,7 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 
 `304`ステータスは、直近のリクエストからリソースが変更されておらず、レスポンスには本文が含まれないことを示しています。 As a bonus, `304` responses don't count against your [rate limit][rate-limiting].
 
-ヤッター！ Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
+Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
 
 * Basic & OAuth認証
 * リポジトリおよびIssueのフェッチと作成
diff --git a/translations/ja-JP/content/rest/guides/index.md b/translations/ja-JP/content/rest/guides/index.md
index 8dca20f533..c4aa670453 100644
--- a/translations/ja-JP/content/rest/guides/index.md
+++ b/translations/ja-JP/content/rest/guides/index.md
@@ -25,4 +25,4 @@ children:
   - /getting-started-with-the-checks-api
 ---
 
-This section of the documentation is intended to get you up-and-running with real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. 認証から結果の操作、結果を他のアプリケーションと組み合わせる方法に至るまで、必要な情報をすべて網羅しています。 ここに挙げる各チュートリアルにはプロジェクトがあり、各プロジェクトはパブリックの[platform-samples](https://github.com/github/platform-samples)に保存・文書化されます。 ![Electrocat](/assets/images/electrocat.png)
+This section of the documentation is intended to get you up-and-running with real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. 認証から結果の操作、結果を他のアプリケーションと組み合わせる方法に至るまで、必要な情報をすべて網羅しています。 ここに挙げる各チュートリアルにはプロジェクトがあり、各プロジェクトはパブリックの[platform-samples](https://github.com/github/platform-samples)に保存・文書化されます。 ![The Octocat](/assets/images/electrocat.png)
diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
index 897f321004..3f3876e5c4 100644
--- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
@@ -24,13 +24,13 @@ topics:
 
 {% ifversion fpt or ghec %}
 
-For information about GitHub's GraphQL API, see the [v4 documentation]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql). For information about migrating to GraphQL, see "[Migrating from REST]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/migrating-from-rest-to-graphql)."
+GitHub の GraphQL API についての情報は、[v4 ドキュメント]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql)を参照してください。 GraphQL への移行についての情報は、「[REST から移行する]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/migrating-from-rest-to-graphql)」を参照してください。
 
 {% endif %}
 
 ## スキーマ
 
-{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  すべてのデータは
+{% ifversion fpt or ghec %}すべての API アクセスは HTTPS 経由で行われ、{% else %}API は{% endif %} `{% data variables.product.api_url_code %}` からアクセスされます。  すべてのデータは
 JSON として送受信されます。
 
 ```shell
@@ -42,9 +42,9 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > Content-Type: application/json; charset=utf-8
 > ETag: "a00049ba79152d03380c34652f2cb612"
 > X-GitHub-Media-Type: github.v3
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4987
-> X-RateLimit-Reset: 1350085394{% ifversion ghes %}
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4987
+> x-ratelimit-reset: 1350085394{% ifversion ghes %}
 > X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %}
 > X-GitHub-Enterprise-Version: GitHub AE{% endif %}
 > Content-Length: 5
@@ -114,7 +114,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/
 Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth App to increase your rate limit. アクセス許可はユーザにのみ付与され、アプリケーションには付与されません。また、認証されていないユーザに表示されるデータのみが返されます。 このため、サーバー間のシナリオでのみ OAuth2 キー/シークレットを使用する必要があります。 Don't leak your OAuth App's client secret to your users.
 
 {% ifversion ghes %}
-プライベートモードでは、OAuth2 キーとシークレットを使用して認証することはできません。認証しようとすると `401 Unauthorized` が返されます。 For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
+プライベートモードでは、OAuth2 キーとシークレットを使用して認証することはできません。認証しようとすると `401 Unauthorized` が返されます。 詳しい情報については、 「[プライベートモードを有効化する](/admin/configuration/configuring-your-enterprise/enabling-private-mode)」を参照してください。
 {% endif %}
 {% endif %}
 
@@ -177,7 +177,7 @@ $ curl {% ifversion fpt or ghae or ghec %}
 
 ## GraphQL グローバルノード ID
 
-See the guide on "[Using Global Node IDs]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
+REST API を介して `node_id` を検索し、それらを GraphQL 操作で使用する方法について詳しくは、「[グローバルノード ID を使用する]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)」のガイドを参照してください。
 
 ## クライアントエラー
 
@@ -251,7 +251,7 @@ API v3 は、可能な限り各アクションに適切な HTTPメソッドを
 
 ## ハイパーメディア
 
-すべてのリソースには、他のリソースにリンクしている 1 つ以上の `*_url` プロパティがある場合があります。  これらは、適切な API クライアントが自分で URL を構築する必要がないように、明示的な URL を提供することを目的としています。  API クライアントには、これらを使用することを強くお勧めしています。  そうすることで、開発者が今後の API のアップグレードを容易に行うことができます。  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
+すべてのリソースには、他のリソースにリンクしている 1 つ以上の `*_url` プロパティがある場合があります。  これらは、適切な API クライアントが自分で URL を構築する必要がないように、明示的な URL を提供することを目的としています。  API クライアントには、これらを使用することを強くお勧めしています。  そうすることで、開発者が今後の API のアップグレードを容易に行うことができます。  すべての URL は、適切な [RFC 6570][rfc] URI テンプレートであることが前提となります。
 
 次に、[uri_template][uri] などを使用して、これらのテンプレートを展開できます。
 
@@ -287,7 +287,7 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
 
 {% endnote %}
 
-The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. 例:
+[Link ヘッダ](https://datatracker.ietf.org/doc/html/rfc5988)には、ページネーション情報が含まれています。 例:
 
     Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
       <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
@@ -298,7 +298,7 @@ _この例は、読みやすいように改行されています。_
 
     Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
 
-This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
+この `Link` レスポンスヘッダには、1 つ以上の[ハイパーメディア](/rest#hypermedia)リンク関係が含まれています。その一部には、[URI テンプレート](https://datatracker.ietf.org/doc/html/rfc6570)としての拡張が必要な場合があります。
 
 使用可能な `rel` の値は以下のとおりです。
 
@@ -365,16 +365,16 @@ API リクエストの返された HTTP ヘッダは、現在のレート制限
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 56
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 56
+> x-ratelimit-reset: 1372700873
 ```
 
 | ヘッダ名                    | 説明                                                                            |
 | ----------------------- | ----------------------------------------------------------------------------- |
-| `X-RateLimit-Limit`     | 1 時間あたりのリクエスト数の上限。                                                            |
-| `X-RateLimit-Remaining` | 現在のレート制限ウィンドウに残っているリクエストの数。                                                   |
-| `X-RateLimit-Reset`     | 現在のレート制限ウィンドウが [UTC エポック秒](http://en.wikipedia.org/wiki/Unix_time)でリセットされる時刻。 |
+| `x-ratelimit-limit`     | 1 時間あたりのリクエスト数の上限。                                                            |
+| `x-ratelimit-remaining` | 現在のレート制限ウィンドウに残っているリクエストの数。                                                   |
+| `x-ratelimit-reset`     | 現在のレート制限ウィンドウが [UTC エポック秒](http://en.wikipedia.org/wiki/Unix_time)でリセットされる時刻。 |
 
 時刻に別の形式を使用する必要がある場合は、最新のプログラミング言語で作業を完了できます。 たとえば、Web ブラウザでコンソールを開くと、リセット時刻を JavaScript の Date オブジェクトとして簡単に取得できます。
 
@@ -388,9 +388,9 @@ new Date(1372700873 * 1000)
 ```shell
 > HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 0
-> X-RateLimit-Reset: 1377013266
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 0
+> x-ratelimit-reset: 1377013266
 
 > {
 >    "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
@@ -406,9 +406,9 @@ If your OAuth App needs to make unauthenticated calls with a higher rate limit,
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4966
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4966
+> x-ratelimit-reset: 1372700873
 ```
 
 {% note %}
@@ -488,9 +488,9 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
 > HTTP/2 304
@@ -498,18 +498,18 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
 > HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 ```
 
 ## オリジン間リソース共有
@@ -522,7 +522,7 @@ API は、任意のオリジンからの AJAX リクエストに対して、オ
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
 HTTP/2 302
 Access-Control-Allow-Origin: *
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
 
 CORS プリフライトリクエストは次のようになります。
@@ -533,7 +533,7 @@ HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 Access-Control-Max-Age: 86400
 ```
 
@@ -547,9 +547,9 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > /**/foo({
 >   "meta": {
 >     "status": 200,
->     "X-RateLimit-Limit": "5000",
->     "X-RateLimit-Remaining": "4966",
->     "X-RateLimit-Reset": "1372700873",
+>     "x-ratelimit-limit": "5000",
+>     "x-ratelimit-remaining": "4966",
+>     "x-ratelimit-reset": "1372700873",
 >     "Link": [ // pagination headers and other links
 >       ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}]
 >     ]
@@ -651,3 +651,4 @@ $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_ur
 [uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
+
diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
index be3e3b9f17..fca0ead997 100644
--- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
@@ -175,6 +175,9 @@ _検索_
 {% ifversion fpt -%}
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif -%}
+{% ifversion ghes > 3.3 -%}
+- [`GET /repos/:owner/:repo/replicas/caches`](/rest/reference/repos#list-repository-cache-replication-status) (:read)
+{% endif -%}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% ifversion fpt -%}
diff --git a/translations/ja-JP/content/rest/reference/pulls.md b/translations/ja-JP/content/rest/reference/pulls.md
index 439647eeda..f5ddb26509 100644
--- a/translations/ja-JP/content/rest/reference/pulls.md
+++ b/translations/ja-JP/content/rest/reference/pulls.md
@@ -45,7 +45,7 @@ Pull Requestには以下のリンク関係が含まれる可能性がありま
 | `review_comments` | Pull Requestの [レビューコメント](/rest/reference/pulls#comments) の API ロケーション。                                            |
 | `review_comment`  | Pull Requestのリポジトリで、[レビューコメント](/rest/reference/pulls#comments)の API ロケーションを構築するための[URL テンプレート](/rest#hypermedia)。 |
 | `commits`         | Pull Requestの [コミット](#list-commits-on-a-pull-request) の API ロケーション。                                               |
-| `statuses`        | Pull Requestの[コミットステータス](/rest/reference/repos#statuses)、すなわち`head` ブランチのステータスの API ロケーション。                       |
+| `statuses`        | Pull Requestの[コミットステータス](/rest/reference/commits#commit-statuses)、すなわち`head` ブランチのステータスの API ロケーション。              |
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/ja-JP/content/rest/reference/scim.md b/translations/ja-JP/content/rest/reference/scim.md
index a3889ff51d..6db0d73edb 100644
--- a/translations/ja-JP/content/rest/reference/scim.md
+++ b/translations/ja-JP/content/rest/reference/scim.md
@@ -33,15 +33,15 @@ SCIM API を使用するには、{% data variables.product.product_name %} Organ
 
 ### サポートされている SCIM ユーザ属性
 
-| 名前               | 種類        | 説明                                                                                                                                                                                                                                             |
-| ---------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName`       | `string`  | ユーザのユーザ名。                                                                                                                                                                                                                                      |
-| `name.givenName` | `string`  | ユーザーの名。                                                                                                                                                                                                                                        |
-| `name.lastName`  | `string`  | ユーザーの姓。                                                                                                                                                                                                                                        |
-| `emails`         | `array`   | ユーザのメール一覧。                                                                                                                                                                                                                                     |
-| `externalId`     | `string`  | この識別子は SAML プロバイダによって生成され、GitHub ユーザと照合するためにSAML プロバイダによって一意の ID として使用されます。 ユーザの `externalID` は、SAML プロバイダ、または [SCIM プロビジョニング済み ID の一覧表示](#list-scim-provisioned-identities)エンドポイントを使用して、ユーザの GitHub ユーザ名やメールアドレスなどの他の既知の属性でフィルタして見つけることができます。 |
-| `id`             | `string`  | GitHub SCIM エンドポイントによって生成された識別子。                                                                                                                                                                                                               |
-| `active`         | `boolean` | ID がアクティブである（true）か、プロビジョニングを解除する必要がある（false）かを示すために使用する。                                                                                                                                                                                      |
+| 名前                | 種類        | 説明                                                                                                                                                                                                                                             |
+| ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName`        | `string`  | ユーザのユーザ名。                                                                                                                                                                                                                                      |
+| `name.givenName`  | `string`  | ユーザーの名。                                                                                                                                                                                                                                        |
+| `name.familyName` | `string`  | ユーザーの姓。                                                                                                                                                                                                                                        |
+| `emails`          | `array`   | ユーザのメール一覧。                                                                                                                                                                                                                                     |
+| `externalId`      | `string`  | この識別子は SAML プロバイダによって生成され、GitHub ユーザと照合するためにSAML プロバイダによって一意の ID として使用されます。 ユーザの `externalID` は、SAML プロバイダ、または [SCIM プロビジョニング済み ID の一覧表示](#list-scim-provisioned-identities)エンドポイントを使用して、ユーザの GitHub ユーザ名やメールアドレスなどの他の既知の属性でフィルタして見つけることができます。 |
+| `id`              | `string`  | GitHub SCIM エンドポイントによって生成された識別子。                                                                                                                                                                                                               |
+| `active`          | `boolean` | ID がアクティブである（true）か、プロビジョニングを解除する必要がある（false）かを示すために使用する。                                                                                                                                                                                      |
 
 {% note %}
 
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
index 3ad64ec237..21d09a4dfa 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
@@ -47,19 +47,19 @@ topics:
 
 `sort:author-date` 修飾子は、オーサー日付を降順または昇順でソートします。
 
-| 修飾子                                            | サンプル                                                                                                                                                                                                                                                  |
-| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sort:author-date` または `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) は、オーサー日付で降順にソートされた、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチします。      |
-| `sort:author-date-asc`                         | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、作者日付の昇順でソートされます。 |
+| 修飾子                                            | サンプル                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:author-date` または `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) は、オーサー日付で降順にソートされた、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチします。                                                        |
+| `sort:author-date-asc`                         | [**`feature org:github sort:author-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending author date. |
 
 ## コミッター日付でソート
 
 `sort:committer-date` 修飾子は、コミッター日付を降順または昇順でソートします。
 
-| 修飾子                                                  | サンプル                                                                                                                                                                                                                                                           |
-| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sort:committer-date` または `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、コミッター日付の降順にソートされます。         |
-| `sort:committer-date-asc`                            | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、コミッター日付の昇順でソートされます。 |
+| 修飾子                                                  | サンプル                                                                                                                                                                                                                                                                                                             |
+| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:committer-date` または `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、コミッター日付の降順にソートされます。                                                           |
+| `sort:committer-date-asc`                            | [**`feature org:github sort:committer-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending committer date. |
 
 ## 更新日付でソート
 
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index c5b4af8ca8..ac555e3632 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -73,9 +73,10 @@ shortTitle: Understand search syntax
 
 検索結果を絞り込む他の方法としては、一定のサブセットを除外することです。 `-` のプリフィックスを修飾子に付けることで、その修飾子にマッチする全ての結果を除外できます。
 
-| クエリ                        | サンプル                                                                                                                                                                                                                    |
-| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>-<em>QUALIFIER</em></code> | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization. |
+| クエリ                        | サンプル                                                                                                                                                                                                                                            |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>QUALIFIER</em></code> | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript. |
+|                            | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization                        |
 
 ## 空白のあるクエリに引用符を使う
 
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-code.md b/translations/ja-JP/content/search-github/searching-on-github/searching-code.md
index 3f07226f3b..07015d6c1d 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-code.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-code.md
@@ -62,11 +62,11 @@ topics:
 
 リポジトリの特定の場所に表示されているソースコードを探すには、`path` 修飾子を使います。 リポジトリの root レベルにあるファイルを検索するには、`path:/` を使います。 または、ディレクトリやそのサブディレクトリ内に存在しているファイルを検索するには、ディレクトリ名もしくはディレクトリへのパスを明示してください。
 
-| 修飾子                        | サンプル                                                                                                                                                                                                                                                                                                                             |
-| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>path:/</code>  | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) は、リポジトリの root レベルに存在する 「octocat」という単語がある _readme_ ファイルにマッチします。                                                                                                                                   |
-| <code>path:<em>DIRECTORY</em></code>  | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the <em>cgi-bin</em> directory, or in any of its subdirectories.                                                                                              |
-| <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
+| 修飾子                        | サンプル                                                                                                                                                                                                                                                                                                                               |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>path:/</code>  | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) は、リポジトリの root レベルに存在する 「octocat」という単語がある _readme_ ファイルにマッチします。                                                                                                                                     |
+| <code>path:<em>DIRECTORY</em></code>  | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the <em>cgi-bin</em> directory, or in any of its subdirectories.                                                                                                |
+| <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
 
 ## 言語で検索
 <!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md
index 1fdf3ebd9d..db9f1b9aaa 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md
@@ -31,10 +31,10 @@ You can only search for packages on {% data variables.product.product_name %}, n
 
 特定のユーザまたは Organization が所有するパッケージを検索するには、`user` 修飾子または `org` 修飾子を使います。
 
-| 修飾子                       | サンプル                                                                                                                                                            |
-| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>user:<em>USERNAME</em></code> | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) は、@codertocat が所有するパッケージにマッチします。                                     |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) は、{% data variables.product.prodname_dotcom %} Organization が所有するパッケージにマッチします。 |
+| 修飾子                       | サンプル                                                                                                                                                                       |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat                                         |
+| <code>org:<em>ORGNAME</em></code> | [**`org:github`**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization |
 
 ## パッケージの可視性によるフィルタリング
 
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
index 1118dd8ef7..e21c236874 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
@@ -111,17 +111,17 @@ shortTitle: Search for repositories
 
 リポジトリのコードの言語に基づいてリポジトリを検索できます。
 
-| 修飾子                       | サンプル                                                                                                                                                         |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) は、JavaScript 形式で記述された「rails」という単語があるリポジトリにマッチします。 |
+| 修飾子                       | サンプル                                                                                                                                                                                    |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. |
 
 ## Topics で検索
 
 特定の Topics で分類されたすべてのリポジトリを見つけることができます。 詳細は「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」を参照してください。
 
-| 修飾子                       | サンプル                                                                                                                                                  |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) は、Topics「jekyll」で分類されたリポジトリにマッチします。 |
+| 修飾子                       | サンプル                                                                                                                                                                                        |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll." |
 
 ## Topics の数で検索
 
@@ -178,10 +178,10 @@ shortTitle: Search for repositories
 
 `help-wanted` ラベルや `good-first-issue` ラベルの付いた Issue の最低数があるリポジトリを、`help-wanted-issues:>n` 修飾子や `good-first-issues:>n` 修飾子によって検索できます。 詳細は、「[ラベルを使用してプロジェクトに役立つコントリビューションを促す](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)」を参照してください。
 
-| 修飾子                        | サンプル                                                                                                                                                                                                               |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) は、「javascript」という単語を含む、`good-first-issue` ラベルが付いた３つ以上の Issue のあるリポジトリにマッチします。 |
-| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) は、「React」という単語を含む、`help-wanted` ラベルが付いた 5 つ以上の Issue のあるリポジトリにマッチします。                 |
+| 修飾子                        | サンプル                                                                                                                                                                                                                                                   |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `good-first-issues:>n`  | [**`good-first-issues:&gt;2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) は、「React」という単語を含む、`help-wanted` ラベルが付いた 5 つ以上の Issue のあるリポジトリにマッチします。                                                     |
 
 ## Search based on ability to sponsor
 
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 88b408b529..817b85fae6 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -103,18 +103,18 @@ shortTitle: Search issues & PRs
 
 `mentions` 修飾子は、特定のユーザーにメンションしている Issue を表示します。 詳細は「[人およびチームにメンションする](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)」を参照してください。
 
-| 修飾子                       | サンプル                                                                                                                                                  |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) は、@defunkt にメンションしている「resque」という単語がある Issue にマッチします。 |
+| 修飾子                       | サンプル                                                                                                                                                            |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>mentions:<em>USERNAME</em></code> | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. |
 
 ## Team メンションで検索
 
 あなたが属する Organization および Team について、 `team` 修飾子により、Organization 内の一定の Team に @メンションしている Issue またはプルリクエストを表示します。 検索を行うには、これらのサンプルの名前をあなたの Organization および Team の名前に置き換えてください。
 
-| 修飾子                       | サンプル                                                                                 |
-| ------------------------- | ------------------------------------------------------------------------------------ |
-| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** は、`@jekyll/owners` Team がメンションされている Issue にマッチします。            |
-|                           | **team:myorg/ops is:open is:pr** は、`@myorg/ops` Team がメンションされているオープンなプルリクエストにマッチします。 |
+| 修飾子                       | サンプル                                                                                  |
+| ------------------------- | ------------------------------------------------------------------------------------- |
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **`team:jekyll/owners`** matches issues where the `@jekyll/owners` team is mentioned. |
+|                           | **team:myorg/ops is:open is:pr** は、`@myorg/ops` Team がメンションされているオープンなプルリクエストにマッチします。  |
 
 ## コメントした人で検索
 
@@ -176,7 +176,7 @@ shortTitle: Search issues & PRs
 
 ## コミットステータスで検索
 
-コミットのステータスでプルリクエストをフィルタリングできます。 This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service.
+コミットのステータスでプルリクエストをフィルタリングできます。 This is especially useful if you are using [the Status API](/rest/reference/commits#commit-statuses) or a CI service.
 
 | 修飾子              | サンプル                                                                                                                                                                                                                     |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -293,17 +293,17 @@ shortTitle: Search issues & PRs
 
 | 修飾子                        | サンプル                                                                                                                                                                                                                     |
 | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) は、2011 年より前にマージされた JavaScript のリポジトリにあるプルリクエストにマッチします。                               |
+| <code>merged:<em>YYYY-MM-DD</em></code> | [**`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011.  |
 |                            | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues)は、2014 年 5 月以降にマージされた、タイトルに「fast」という単語がある Ruby のプルリクエストにマッチします。 |
 
 ## プルリクエストがマージされているかどうかで検索
 
 `is` 修飾子を使って、マージされたかどうかでプルリクエストをフィルタリングできます。
 
-| 修飾子           | サンプル                                                                                                                                               |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `is:merged`   | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) は、「bugfix」という単語がある、マージされたプルリクエストにマッチします。 |
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) は、「error」という単語がある、クローズされた Issue およびプルリクエストにマッチします。   |
+| 修飾子           | サンプル                                                                                                                                                     |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bug." |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) は、「error」という単語がある、クローズされた Issue およびプルリクエストにマッチします。         |
 
 ## リポジトリがアーカイブされているかどうかで検索
 
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
index 99bc4e5d2c..955f879917 100644
--- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -49,6 +49,43 @@ shortTitle: Manage payment tiers
 {% data reusables.sponsors.tier-update %}
 {% data reusables.sponsors.retire-tier %}
 
+## Adding a repository to a sponsorship tier
+
+{% data reusables.sponsors.sponsors-only-repos %}
+
+### About adding repositories to a sponsorship tier
+
+To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository.
+
+When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled.
+
+Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier.
+
+You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync.
+
+### About transfers for repositories that are added to sponsorship tiers
+
+If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected.
+
+- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors.
+- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository.
+- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository.
+
+### Adding a repository a sponsorship tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+1. Select **Grant sponsors access to a private repository**.
+
+   ![Screenshot of checkbox to grant sponsors access to a private repository](/assets/images/help/sponsors/grant-sponsors-access-to-repo-checkbox.png)
+
+1. Select the dropdown menu and click the repository you want to add.
+
+   ![Screenshot of dropdown menu to choose the repository to grant sponsors access to](/assets/images/help/sponsors/grant-sponsors-access-to-repo-dropdown.png)
+
+{% data reusables.sponsors.tier-update %}
+
 ## カスタム金額の層を有効化する
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
diff --git a/translations/ja-JP/data/features/code-scanning-task-lists.yml b/translations/ja-JP/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..0de30490f7
--- /dev/null
+++ b/translations/ja-JP/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/translations/ja-JP/data/features/codeql-ml-queries.yml b/translations/ja-JP/data/features/codeql-ml-queries.yml
new file mode 100644
index 0000000000..c74f86b77f
--- /dev/null
+++ b/translations/ja-JP/data/features/codeql-ml-queries.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5604.
+#Documentation for the beta release of CodeQL queries boosted by machine learning
+#to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/ja-JP/data/features/github-actions-in-dependency-graph.yml b/translations/ja-JP/data/features/github-actions-in-dependency-graph.yml
new file mode 100644
index 0000000000..1690a6b771
--- /dev/null
+++ b/translations/ja-JP/data/features/github-actions-in-dependency-graph.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5813.
+#Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
+versions:
+  fpt: '*'
+  ghae: 'issue-5813'
+  ghec: '*'
diff --git a/translations/ja-JP/data/features/security-overview-views.yml b/translations/ja-JP/data/features/security-overview-views.yml
new file mode 100644
index 0000000000..bef4f54c9d
--- /dev/null
+++ b/translations/ja-JP/data/features/security-overview-views.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5503.
+#Documentation for the security overview individual views
+versions:
+  ghes: '> 3.4'
+  ghae: 'issue-5503'
+  ghec: '*'
diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml
index 0d07b17cb3..8d45b89496 100644
--- a/translations/ja-JP/data/learning-tracks/actions.yml
+++ b/translations/ja-JP/data/learning-tracks/actions.yml
@@ -41,6 +41,7 @@ adopting_github_actions_for_your_enterprise:
   title: 'Adopt GitHub Actions for your enterprise'
   description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
   guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
     - /actions/learn-github-actions/understanding-github-actions
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
diff --git a/translations/ja-JP/data/learning-tracks/admin.yml b/translations/ja-JP/data/learning-tracks/admin.yml
index b918b1009b..6cceba3ea6 100644
--- a/translations/ja-JP/data/learning-tracks/admin.yml
+++ b/translations/ja-JP/data/learning-tracks/admin.yml
@@ -42,6 +42,7 @@ adopting_github_actions_for_your_enterprise:
   title: 'Adopt GitHub Actions for your enterprise'
   description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
   guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
     - /actions/learn-github-actions/understanding-github-actions
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
diff --git a/translations/ja-JP/data/product-examples/README.md b/translations/ja-JP/data/product-examples/README.md
index 376df32544..616c8043e6 100644
--- a/translations/ja-JP/data/product-examples/README.md
+++ b/translations/ja-JP/data/product-examples/README.md
@@ -2,7 +2,7 @@
 
 `product-landing`レイアウトを使うページは、`Examples`セクションを含むことができます。 現在は、3種類の例をサポートしています。
 
-1. コードサンプル https://docs.github.com/en/actions#code-examplesを参照してください。
+1. コードサンプル https://docs.github.com/en/codespaces#code-examplesを参照してください。
 
 2. コミュニティサンプル https://docs.github.com/en/discussions#community-examplesを参照してください。
 
@@ -10,7 +10,7 @@
 
 ## 動作の仕組み
 
-それぞれの製品のサンプルデータは、`data/product-landing-examples`内の、**製品**の名前のサブディレクトリと**example type**という名前のYMLファイル（たとえば`data/product-examples/sponsors/user-examples.yml`あるいは`data/product-examples/actions/code-examples.yml`）中で定義されています。 現在は、製品ごとに1種類の例のみをサポートしています。
+Example data for each product is defined in `data/product-landing-examples`, in a subdirectory named for the **product** and a YML file named for the **example type** (e.g., `data/product-examples/sponsors/user-examples.yml` or `data/product-examples/codespaces/code-examples.yml`). 現在は、製品ごとに1種類の例のみをサポートしています。
 
 ### バージョン管理
 
diff --git a/translations/ja-JP/data/product-examples/actions/code-examples.yml b/translations/ja-JP/data/product-examples/actions/code-examples.yml
deleted file mode 100644
index ea6a77eed5..0000000000
--- a/translations/ja-JP/data/product-examples/actions/code-examples.yml
+++ /dev/null
@@ -1,335 +0,0 @@
----
-- 
-  title: サービスの例
-  description: サービスコンテナを使うワークフローの例
-  languages: JavaScript
-  href: actions/example-services
-  tags:
-    - サービスコンテナ
-- 
-  title: GitHubラベルを宣言的にセットアップ
-  description: リポジトリ間にわたってラベルを宣言的にセットアップするGitHub Actions
-  languages: JavaScript
-  href: lannonbr/issue-label-manager-action
-  tags:
-    - issues
-    - labels
-- 
-  title: 宣言的にGitHubラベルを同期
-  description: 宣言的な方法でGitHubラベルを同期するGitHub Action
-  languages: 'Go, Dockerfile'
-  href: micnncim/action-label-syncer
-  tags:
-    - issues
-    - labels
-- 
-  title: GitHubへのリリースの追加
-  description: アクションでGitHubリリースを公開
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Github-Release-Action
-  tags:
-    - releases
-    - 公開
-- 
-  title: Dockerhubにdockerイメージを公開
-  description: Dockerイメージのビルドと公開に使われるGitHub Action
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Publish-Docker-Github-Action
-  tags:
-    - docker
-    - 公開
-    - ビルド
-- 
-  title: ファイルからの内容を使ってIssueを作成
-  description: ファイルからの内容を利用してIssueを作成するGitHub Action
-  languages: 'JavaScript, Python'
-  href: peter-evans/create-issue-from-file
-  tags:
-    - issues
-- 
-  title: アセット付きでGitHubリリースを公開
-  description: GitHubリリースを作成するGitHub Action
-  languages: 'TypeScript, Shell, JavaScript'
-  href: softprops/action-gh-release
-  tags:
-    - releases
-    - 公開
-- 
-  title: GitHubプロジェクトオートメーション+
-  description: 任意のwebhookイベントでGitHubプロジェクトカードを自動化
-  languages: JavaScript
-  href: alex-page/github-project-automation-plus
-  tags:
-    - projects
-    - 自動化
-    - issues
-    - pull requests
-- 
-  title: WebインターフェースでGitHub Actionsをローカル実行
-  description: GitHub Actionsワークフローをローカルで実行（local）
-  languages: 'JavaScript, HTML, Dockerfile, CSS'
-  href: phishy/wflow
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: GitHub Actionsをローカルで実行
-  description: ターミナル内でGitHub Actionsをローカルで実行
-  languages: 'Go, Shell'
-  href: nektos/act
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: AndroidのデバッグAPKをビルド及び公開
-  description: デバッグAPKをAndroidプロジェクトからビルド及びリリース
-  languages: 'Shell, Dockerfile'
-  href: ShaunLWM/action-release-debugapk
-  tags:
-    - android
-    - ビルド
-- 
-  title: GitHub Actions用の連続したビルド番号の生成
-  description: 連続したビルド番号を生成するためのGitHub Action
-  languages: JavaScript
-  href: einaregilsson/build-number
-  tags:
-    - ビルド
-    - 自動化
-- 
-  title: リポジトリにプッシュバックするGitHub Action
-  description: 認証の問題なくGitHubリポジトリにGitの変更をプッシュ
-  languages: 'JavaScript, Shell'
-  href: ad-m/github-push-action
-  tags:
-    - 公開
-- 
-  title: イベントに基づいてリリースノートを生成
-  description: イベントに基づいてリリースノートを自動生成するアクション
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/release-notes-generator-action
-  tags:
-    - releases
-    - 公開
-- 
-  title: 提供されたMarkdownファイルに基づいてGitHub wikiページを生成
-  description: 提供されたMarkdownファイルに基づいてGitHub wikiページを生成
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/wiki-page-creator-action
-  tags:
-    - wiki
-    - 公開
-- 
-  title: Pull Requestを自動的に魔法のようにラベル付け（コミットされたファイルを使用）
-  description: Pull Requestを自動的に魔法のようにラベル付けするGitHub Action（コミットされたファイルを使用）
-  languages: 'TypeScript, Dockerfile, JavaScript'
-  href: Decathlon/pull-request-labeler-action
-  tags:
-    - projects
-    - issues
-    - labels
-- 
-  title: 作者のTeam名に基づいてPull Requestにラベルを追加
-  description: 作者名に基づいてPull Requestをラベル付けするGitHub Action
-  languages: 'TypeScript, JavaScript'
-  href: JulienKode/team-labeler-action
-  tags:
-    - プルリクエスト
-    - labels
-- 
-  title: PR/プッシュによるファイル変更のリスト取得
-  description: このアクションで、リポジトリ中で変更されたファイルの出力が得られます。
-  languages: 'TypeScript, Shell, JavaScript'
-  href: trilom/file-changes-action
-  tags:
-    - ワークフロー
-    - リポジトリ
-- 
-  title: 任意のワークフロー中のプライベートアクション
-  description: プライベートのGitHub Actionsを容易に再利用できるようにします
-  languages: 'TypeScript, JavaScript, Shell'
-  href: InVisionApp/private-action-loader
-  tags:
-    - ワークフロー
-    - tools
-- 
-  title: Issueの内容を使ってIssueにラベル付けします
-  description: ラベルとアサインされた人で自動的にIssueにタグ付けするGitHub Action
-  languages: 'JavaScript, TypeScript'
-  href: damccorm/tag-ur-it
-  tags:
-    - ワークフロー
-    - tools
-    - labels
-    - issues
-- 
-  title: GitHubリリースのロールバック
-  description: リリースをロールバックあるいは削除するGitHub Action
-  languages: 'JavaScript'
-  href: author/action-rollback
-  tags:
-    - ワークフロー
-    - releases
-- 
-  title: クローズされたIssue及びPull Requestのロック
-  description: 一定期間アクティビティのなかったあとにクローズされたIssueやPull RequestをロックするGitHub Action
-  languages: 'JavaScript'
-  href: dessant/lock-threads
-  tags:
-    - issues
-    - pull requests
-    - ワークフロー
-- 
-  title: 2つのブランチ間のコミットの差異数の取得
-  description: このGitHub Actionは2つのブランチを比較し、それらの間のコミットカウントを返します。
-  languages: 'JavaScript, Shell'
-  href: jessicalostinspace/commit-difference-action
-  tags:
-    - コミット
-    - diff
-    - ワークフロー
-- 
-  title: Git参照に基づくリリースノートを生成
-  description: changelogとリリースノートを生成するGitHub Action
-  languages: 'JavaScript, Shell'
-  href: metcalfc/changelog-generator
-  tags:
-    - cicd
-    - release-notes
-    - ワークフロー
-    - 変更履歴
-- 
-  title: GitHubリポジトリとコミットにポリシーを適用する
-  description: パイプラインに対するポリシーの適用
-  languages: 'Go, Makefile, Dockerfile, Shell'
-  href: talos-systems/conform
-  tags:
-    - docker
-    - build-automation
-    - ワークフロー
-- 
-  title: Issueに基づく自動ラベル
-  description: Issueの説明に基づいてIssueに自動的にラベル付け
-  languages: 'TypeScript, JavaScript, Dockerfile'
-  href: Renato66/auto-label
-  tags:
-    - labels
-    - ワークフロー
-    - 自動化
-- 
-  title: 設定されたGitHub Actionsを最新バージョンにアップデート
-  description: すべてのアクションが最新かどうかをチェックするCLIツール
-  languages: 'C#, Inno Setup, PowerShell, Shell'
-  href: fabasoad/ghacu
-  tags:
-    - versions
-    - cli
-    - ワークフロー
-- 
-  title: Issueブランチの作成
-  description: Issueブランチの作成を自動化するGitHub Action
-  languages: 'JavaScript, Shell'
-  href: robvanderleek/create-issue-branch
-  tags:
-    - probot
-    - issues
-    - labels
-- 
-  title: 古い成果物を削除
-  description: 成果物のクリーンアップをカスタマイズ
-  languages: 'JavaScript, Shell'
-  href: c-hive/gha-remove-artifacts
-  tags:
-    - 成果物
-    - ワークフロー
-- 
-  title: 定義されたファイル/バイナリをWikiあるいは外部リポジトリと同期
-  description: 変更を、たとえばwikiのような外部リポジトリに自動的に同期するGitHub Action
-  languages: 'Shell, Dockerfile'
-  href: kai-tub/external-repo-sync-action
-  tags:
-    - wiki
-    - 同期
-    - ワークフロー
-- 
-  title: 任意のファイルに基づいてGitHub Wikiページを作成/更新/削除
-  description: ファイルとディレクトリの除外、そして実際のファイルの削除をできるようにしながら、rsyncを使ってGitHub wikiを更新
-  languages: 'Shell, Dockerfile'
-  href: Andrew-Chen-Wang/github-wiki-action
-  tags:
-    - wiki
-    - docker
-    - ワークフロー
-- 
-  title: Prow GitHub Actions
-  description: ポリシー適用の自動化、chat-ops、自動PRマージ
-  languages: 'TypeScript, JavaScript'
-  href: jpmcb/prow-github-actions
-  tags:
-    - chat-ops
-    - prow
-    - ワークフロー
-- 
-  title: ワークフロー中でのGitHubステータスのチェック
-  description: ワークフロー中でのGitHubステータスのチェック
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-status
-  tags:
-    - ステータス
-    - モニタリング
-    - ワークフロー
-- 
-  title: GitHub上でラベルをコードとして管理
-  description: ラベルを管理（作成/名前の変更/更新/削除）をするGitHub Action
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-labeler
-  tags:
-    - labels
-    - ワークフロー
-    - 自動化
-- 
-  title: フリーでオープンソースのプロジェクトに資金を分配
-  description: プロジェクトのコントリビューター及び依存関係への資金の継続的配分
-  languages: 'Python, Dockerfile, Shell, Ruby'
-  href: protontypes/libreselery
-  tags:
-    - sponsors
-    - 資金
-    - payment
-- 
-  title: GitHubの先駆者ルール
-  description: PRへのレビュー担当者、サブスクライバー、ラベル、アサインされた人の追加
-  languages: 'TypeScript, JavaScript'
-  href: gagoar/use-herald-action
-  tags:
-    - reviewers
-    - labels
-    - assignees
-    - プルリクエスト
-- 
-  title: コードオーナーバリデータ
-  description: パブリック及びプライベートのGitHubリポジトリと、GitHub Enterpriseの環境もサポートする、GitHub CODEOWNERSファイルの正確性の保証
-  languages: 'Go, Shell, Makefile, Dockerfile'
-  href: mszostok/codeowners-validator
-  tags:
-    - コードオーナー
-    - 検証
-    - ワークフロー
-- 
-  title: Copybara Action
-  description: リポジトリ間でコードを移動して変換（1つの単一リポジトリから複数のリポジトリを管理するのに理想的）
-  languages: 'TypeScript, JavaScript, Shell'
-  href: olivr/copybara-action
-  tags:
-    - 単一リポジトリ
-    - copybara
-    - ワークフロー
-- 
-  title: 静的ファイルをGitHub Pagesにデプロイ
-  description: WebサイトをGitHub Pagesに自動的に公開するGitHub Action
-  languages: 'TypeScript, JavaScript'
-  href: peaceiris/actions-gh-pages
-  tags:
-    - 公開
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-20/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-20/13.yml
index 4afe078054..ce458f931c 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/2-20/13.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/2-20/13.yml
@@ -2,8 +2,8 @@
 date: '2020-08-11'
 sections:
   security_fixes:
-    - '**重大:** 攻撃者がGitHub Pagesのサイトの構築の一部としてコマンドを実行できる、リモートコード実行の脆弱性がGitHub Pagesで特定されました。この問題は、Pagesのビルドプロセスで使われている古くて脆弱性のある依存関係によるものです。この脆弱性を突くには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成して構築する権限を持っていなければなりません。この脆弱性は、GitHub Enterprise Serverのすべてのバージョンに影響します。この脆弱性を緩和するために、CVE-2020-14001への対応でkramdownがアップデートされました。{% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
-    - '**高:** GitHub Enterprise Server上で実行されるGitのサブコマンドに、攻撃者が悪意ある引数をインジェクトすることができました。これによって、攻撃者は部分的にユーザが制御する内容で任意のファイルを上書きでき、GitHub Enterprise Serverインスタンス上で任意のコマンドを実行できる可能性がありました。この脆弱性を突くためには、攻撃者はGitHub Enterprise Serverインスタンス内のリポジトリへのアクセス権限を持っていなければなりません。しかし、他の保護があるので、この脆弱性を積極的に突く方法は特定できませんでした。この脆弱性はGitHub Security Bug Bountyプログラムを通じて報告されました。{% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance.  This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
+    - '**High:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
     - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
   bugs:
     - 'Consulの設定エラーによって、スタンドアローンインスタンス上で処理されないバックグランドジョブがありました。{% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml
index b5622c9f32..01f9c1eed7 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml
@@ -2,7 +2,7 @@ date: '2020-08-26'
 sections:
   security_fixes:
     - >-
-      **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
+      {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
       https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}
     - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}'
     - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-21/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-21/4.yml
index 16e8cb7ea7..5a816a54cf 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/2-21/4.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/2-21/4.yml
@@ -2,8 +2,8 @@
 date: '2020-08-11'
 sections:
   security_fixes:
-    - '**重大:** 攻撃者がGitHub Pagesのサイトの構築の一部としてコマンドを実行できる、リモートコード実行の脆弱性がGitHub Pagesで特定されました。この問題は、Pagesのビルドプロセスで使われている古くて脆弱性のある依存関係によるものです。この脆弱性を突くには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成して構築する権限を持っていなければなりません。この脆弱性は、GitHub Enterprise Serverのすべてのバージョンに影響します。この脆弱性を緩和するために、CVE-2020-14001への対応でkramdownがアップデートされました。 {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
-    - '**高:** GitHub Enterprise Server上で実行されるGitのサブコマンドに、攻撃者が悪意ある引数をインジェクトすることができました。これによって、攻撃者は部分的にユーザが制御する内容で任意のファイルを上書きでき、GitHub Enterprise Serverインスタンス上で任意のコマンドを実行できる可能性がありました。この脆弱性を突くためには、攻撃者はGHESインスタンス内のリポジトリへのアクセス権限を持っていなければなりません。しかし、他の保護があるので、この脆弱性を積極的に突く方法は特定できませんでした。この脆弱性はGitHub Security Bug Bountyプログラムを通じて報告されました。{% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance.  This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
+    - '**High:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
     - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
   bugs:
     - 'Consulの設定エラーによって、スタンドアローンインスタンス上で処理されないバックグランドジョブがありました。{% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml
index f8d72193cd..c9ef772868 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml
@@ -2,9 +2,9 @@ date: '2020-08-26'
 sections:
   security_fixes:
     - >-
-      **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
+      {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
       https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %}
-    - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
+    - '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
     - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
   bugs:
     - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml
index 75c2b52ce7..24db3b54fd 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/21.yml
@@ -3,6 +3,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions.
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.
     - A misconfiguration in the Management Console caused scheduling errors.
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/22.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/22.yml
index 073406d0ad..d2f0b70c38 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/22.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/22.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/24.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/24.yml
new file mode 100644
index 0000000000..8dec6e1579
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/24.yml
@@ -0,0 +1,21 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。
+    - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。
+    - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/13.yml
index f819ab8c9e..a0c7d7c269 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/13.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/13.yml
@@ -2,6 +2,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions. 
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. 
     - A misconfiguration in the Management Console caused scheduling errors. 
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/14.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/14.yml
index ffe4e66705..5a7f55939a 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/14.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/14.yml
@@ -1,7 +1,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/16.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/16.yml
new file mode 100644
index 0000000000..7fd3cbeeed
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/16.yml
@@ -0,0 +1,24 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - Several documentation links resulted in a 404 Not Found error.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`.
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml
index 3097ad337d..7849ed1f99 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/5.yml
@@ -3,6 +3,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions.
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.`
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/6.yml
index 4e8d210d8c..46da63fcf0 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/6.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/6.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml
new file mode 100644
index 0000000000..78a2cdf79b
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/8.yml
@@ -0,0 +1,26 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。
+    - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
+    - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/1.yml
index db0b87bc44..f61c17b882 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/1.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/1.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml
new file mode 100644
index 0000000000..fdb271099e
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/3.yml
@@ -0,0 +1,29 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - '**MEDIUM**:  Secret Scanning API calls could return alerts for repositories outside the scope of the request.'
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
+    - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
diff --git a/translations/ja-JP/data/reusables/actions/oidc-permissions-token.md b/translations/ja-JP/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..ddc4d1f443
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,13 @@
+The job or workflow run requires a `permissions` setting with [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). This allows the JWT to be requested from GitHub's OIDC provider using one of these approaches:
+
+- Using environment variables on the runner (`ACTIONS_ID_TOKEN_REQUEST_URL` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Using `getIDToken()` from the Actions toolkit.
+
+If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
+
+```yaml{:copy}
+permissions:
+  id-token: write
+```
+
+You may need to specify additional permissions here, depending on your workflow's requirements. 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
index 593eefe8b4..5297e0f155 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -52,7 +52,7 @@ on:
       - '!sub-project/docs/**'
 ```
 
-### Git diffの比較
+#### Git diffの比較
 
 {% note %}
 
diff --git a/translations/ja-JP/data/reusables/apps/checks-availability.md b/translations/ja-JP/data/reusables/apps/checks-availability.md
index 411a710ae3..eb79d843d9 100644
--- a/translations/ja-JP/data/reusables/apps/checks-availability.md
+++ b/translations/ja-JP/data/reusables/apps/checks-availability.md
@@ -1 +1 @@
-Checks APIのための書き込み権限は、GitHub Appsだけが利用できます。 OAuth App及び認証されたユーザは、チェック実行とチェックスイートを見ることができますが、作成することはできません。 GitHub Appを構築しているのでないなら、[ステータスAPI](/rest/reference/repos#statuses)に興味を引かれるかもしれません。
+Checks APIのための書き込み権限は、GitHub Appsだけが利用できます。 OAuth App及び認証されたユーザは、チェック実行とチェックスイートを見ることができますが、作成することはできません。 GitHub Appを構築しているのでないなら、[ステータスAPI](/rest/reference/commits#commit-statuses)に興味を引かれるかもしれません。
diff --git a/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index aa4ac0a10c..4946b33d9e 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else  %}
 1. 設定のサイドバーで、**Audit log**をクリックしてください。 ![サイドバー内のOrg Audit log設定](/assets/images/help/organizations/org-settings-audit-log.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index e31cc594fa..1aae695aa1 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else  %}
 3. 左のサイドバーで**Audit log**をクリックしてください。 ![Audit logタブ](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/billing/license-statuses.md b/translations/ja-JP/data/reusables/billing/license-statuses.md
new file mode 100644
index 0000000000..eea8e721f5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/billing/license-statuses.md
@@ -0,0 +1,6 @@
+{% ifversion ghec %}
+If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
+- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
+- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
+- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
index 7db5b9879a..6664cbfafc 100644
--- a/translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 
 {% note %}
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
new file mode 100644
index 0000000000..133b760b30
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -0,0 +1,9 @@
+{% if codeql-ml-queries %}
+
+{% note %}
+
+**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
new file mode 100644
index 0000000000..d6a26bd47f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -0,0 +1,5 @@
+以下のクエリスイートは{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}に組み込まれており、利用可能です。
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% if codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites.md b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites.md
index 52778c76ec..1da1d60bb1 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites.md
@@ -1,8 +1,4 @@
-以下のクエリスイートは{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}に組み込まれており、利用可能です。
-
   | クエリスイート                | 説明                                           |
   |:---------------------- |:-------------------------------------------- |
   | `security-extended`    | デフォルトのクエリよりも重要度と精度が低いクエリ                     |
   | `security-and-quality` | `security-extended` からのクエリ、および保守性と信頼性に関するクエリ |
-
-クエリスイートを指定すると、{% data variables.product.prodname_codeql %}の分析エンジンは、デフォルトのクエリセットに加えてスイート内に含まれるクエリを実行します。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
index 754d7d0275..394f39607f 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
 {% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage.
 
 ### Calculating compute usage
-The total number of uptime minutes for which the {% data variables.product.prodname_codespaces %} instances are active. Compute usage is calculated by the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
+Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
 
-Uptime is controlled by stopping your codespace which can be done manually or based on period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
 
 ### Calculating storage usage
 For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-secrets-button.md b/translations/ja-JP/data/reusables/dependabot/dependabot-secrets-button.md
index 090e35d2e2..0971d5d0b8 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-secrets-button.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-secrets-button.md
@@ -1,2 +1,5 @@
-1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**.{% ifversion fpt or ghec %} ![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/help/dependabot/dependabot-secrets.png){% else %}
-![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png){% endif %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
+{% elsif ghes > 3.2%}
+1. サイドバーで**{% data variables.product.prodname_dependabot %}**をクリックしてください。 ![{% data variables.product.prodname_dependabot %}シークレットサイドバーオプション](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md
index 5d4180b8ef..21c3437455 100644
--- a/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md
@@ -1 +1 @@
-If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)."
+If you need to reset the password for your setup user, contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/save-settings.md b/translations/ja-JP/data/reusables/enterprise_management_console/save-settings.md
index cc7e996807..a0a2bf8628 100644
--- a/translations/ja-JP/data/reusables/enterprise_management_console/save-settings.md
+++ b/translations/ja-JP/data/reusables/enterprise_management_console/save-settings.md
@@ -1,2 +1,2 @@
 1. 左のサイドバーの下で**Save settings（設定の保存）**をクリックしてください。 ![{% data variables.enterprise.management_console %} での [Save settings] ボタン](/assets/images/enterprise/management-console/save-settings.png)
-1. 設定が完了するのを待ってください。
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..a1cc2ae3c0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.product.product_location %}.
+
+{% endwarning %}
diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..5d2f0d6d09
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,3 @@
+1. 設定が完了するのを待ってください。
+
+   ![インスタンスの設定](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/translations/ja-JP/data/reusables/gated-features/user-repo-collaborators.md b/translations/ja-JP/data/reusables/gated-features/user-repo-collaborators.md
index 6790174f0d..319b8698fd 100644
--- a/translations/ja-JP/data/reusables/gated-features/user-repo-collaborators.md
+++ b/translations/ja-JP/data/reusables/gated-features/user-repo-collaborators.md
@@ -1 +1,4 @@
-{% data variables.product.prodname_free_user %}を使用している場合、パブリック及びプライベートリポジトリで無制限にコラボレータを追加できます。
+{% ifversion fpt %}
+If you're using
+{% data variables.product.prodname_free_user %}, you can add unlimited collaborators on public and private repositories.
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-activity-types.md b/translations/ja-JP/data/reusables/github-actions/actions-activity-types.md
new file mode 100644
index 0000000000..ecc88a10cb
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/actions-activity-types.md
@@ -0,0 +1,22 @@
+Some events have activity types that give you more control over when your workflow should run. Use `on.<event_name>.types` to define the type of event activity that will trigger a workflow run.
+
+For example, the `issue_comment` event has the `created`, `edited`, and `deleted` activity types. If your workflow triggers on the `label` event, it will run whenever a label is created, edited, or deleted. If you specify the `created` activity type for the `label` event, your workflow will run when a label is created but not when a label is edited or deleted.
+
+```yaml
+on:
+  label:
+    types:
+      - created
+```
+
+If you specify multiple activity types, only one of those event activity types needs to occur to trigger your workflow. If multiple triggering event activity types for your workflow occur at the same time, multiple workflow runs will be triggered. For example, the following workflow triggers when an issue is opened or labeled. If an issue with two labels is opened, three workflow runs will start: one for the issue opened event and two for the two issue labeled events.
+
+```yaml
+on:
+  issue:
+    types:
+      - opened
+      - labeled
+```
+
+各イベントとそのアクティビティタイプの詳細については、「[ワークフローをトリガーするイベント](/actions/using-workflows/events-that-trigger-workflows)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-filters.md b/translations/ja-JP/data/reusables/github-actions/actions-filters.md
new file mode 100644
index 0000000000..549ef0190e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/actions-filters.md
@@ -0,0 +1,11 @@
+Some events have filters that give you more control over when your workflow should run.
+
+For example, the `push` event has a `branches` filter that causes your workflow to run only when a push to a branch that matches the `branches` filter occurs, instead of when any push occurs.
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+      - 'releases/**'
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-multiple-types.md b/translations/ja-JP/data/reusables/github-actions/actions-multiple-types.md
new file mode 100644
index 0000000000..411e4c598e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/actions-multiple-types.md
@@ -0,0 +1,18 @@
+If you specify activity types or filters for an event and your workflow triggers on multiple events, you must configure each event separately. 設定を持たないイベントも含め、すべてのイベントにはコロン (`:`)を追加しなければなりません。
+
+For example, a workflow with the following `on` value will run when:
+
+- A label is created
+- A push is made to the `main` branch in the repository
+- A push is made to a {% data variables.product.prodname_pages %}-enabled branch
+
+```yaml
+on:
+  label:
+    types:
+      - created
+  push:
+    branches:
+      - main
+  page_build:
+```
diff --git a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md
index 1fe230801f..26d4a25747 100644
--- a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md
+++ b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md
@@ -1,75 +1,19 @@
 ### Using a single event
 
-For example, a workflow with the following `on` value will run when a push is made to any branch in the workflow's repository:
-
-```yaml
-on: push
-```
+{% data reusables.github-actions.on-single-example %}
 
 ### Using multiple events
 
-You can specify a single event or multiple events. For example, a workflow with the following `on` value will run when a push is made to any branch in the repository or when someone forks the repository:
-
-```yaml
-on: [push, fork]
-```
-
-If you specify multiple events, only one of those events needs to occur to trigger your workflow. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered.
+{% data reusables.github-actions.on-multiple-example %}
 
 ### Using activity types
 
-Some events have activity types that give you more control over when your workflow should run.
-
-For example, the `issue_comment` event has the `created`, `edited`, and `deleted` activity types. If your workflow triggers on the `label` event, it will run whenever a label is created, edited, or deleted. If you specify the `created` activity type for the `label` event, your workflow will run when a label is created but not when a label is edited or deleted.
-
-```yaml
-on:
-  label:
-    types:
-      - created
-```
-
-If you specify multiple activity types, only one of those event activity types needs to occur to trigger your workflow. If multiple triggering event activity types for your workflow occur at the same time, multiple workflow runs will be triggered. For example, the following workflow triggers when an issue is opened or labeled. If an issue with two labels is opened, three workflow runs will start: one for the issue opened event and two for the two issue labeled events.
-
-```yaml
-on:
-  issue:
-    types:
-      - opened
-      - labeled
-```
+{% data reusables.github-actions.actions-activity-types %}
 
 ### Using filters
 
-Some events have filters that give you more control over when your workflow should run.
-
-For example, the `push` event has a `branches` filter that causes your workflow to run only when a push to a branch that matches the `branches` filter occurs, instead of when any push occurs.
-
-```yaml
-on:
-  push:
-    branches:
-      - main
-      - 'releases/**'
-```
+{% data reusables.github-actions.actions-filters %}
 
 ### Using activity types and filters with multiple events
 
-If you specify activity types or filters for an event and your workflow triggers on multiple events, you must configure each event separately. 設定を持たないイベントも含め、すべてのイベントにはコロン (`:`)を追加しなければなりません。
-
-For example, a workflow with the following `on` value will run when:
-
-- A label is created
-- A push is made to the `main` branch in the repository
-- A push is made to a {% data variables.product.prodname_pages %}-enabled branch
-
-```yaml
-on:
-  label:
-    types:
-      - created
-  push:
-    branches:
-      - main
-  page_build:
-```
\ No newline at end of file
+{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/on-multiple-example.md b/translations/ja-JP/data/reusables/github-actions/on-multiple-example.md
new file mode 100644
index 0000000000..66a7708123
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/on-multiple-example.md
@@ -0,0 +1,7 @@
+You can specify a single event or multiple events. For example, a workflow with the following `on` value will run when a push is made to any branch in the repository or when someone forks the repository:
+
+```yaml
+on: [push, fork]
+```
+
+If you specify multiple events, only one of those events needs to occur to trigger your workflow. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered.
diff --git a/translations/ja-JP/data/reusables/github-actions/on-single-example.md b/translations/ja-JP/data/reusables/github-actions/on-single-example.md
new file mode 100644
index 0000000000..b8c7046c3e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/on-single-example.md
@@ -0,0 +1,5 @@
+For example, a workflow with the following `on` value will run when a push is made to any branch in the workflow's repository:
+
+```yaml
+on: push
+```
diff --git a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-options.md b/translations/ja-JP/data/reusables/github-actions/private-repository-forks-options.md
new file mode 100644
index 0000000000..8d524e6c53
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/private-repository-forks-options.md
@@ -0,0 +1,3 @@
+- **Run workflows from fork pull requests（フォークのPull Requestからワークフローを実行）** - 読み取りのみの権限を持ち、シークレットにはアクセスできない`GITHUB_TOKEN`を使って、フォークのPull Requestからワークフローを実行することをユーザに許可します。
+- **Send write tokens to workflows from pull requests（Pull Requestから書き込みトークンをワークフローに送信）** - 書き込み権限を持つ`GITHUB_TOKEN`の利用をフォークからのPull Requestに許可します。
+- **Send secrets to workflows from pull requests（Pull Requestからワークフローにシークレットを送信）** - すべてのシークレットをPull Requestから利用可能にします。
diff --git a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md b/translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md
index 9280ed2e45..fab5c6c6d8 100644
--- a/translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md
+++ b/translations/ja-JP/data/reusables/github-actions/private-repository-forks-overview.md
@@ -1,5 +1 @@
-プライベートリポジトリのフォークの利用に依存しているなら、ユーザがどのように`pull_request`イベントの際にワークフローを実行できるかを制御するポリシーを設定できます。 Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.{% ifversion ghec or ghes or ghae %} For enterprises, the policies are applied to all repositories in all organizations.{% endif %}
-
-- **Run workflows from fork pull requests（フォークのPull Requestからワークフローを実行）** - 読み取りのみの権限を持ち、シークレットにはアクセスできない`GITHUB_TOKEN`を使って、フォークのPull Requestからワークフローを実行することをユーザに許可します。
-- **Send write tokens to workflows from pull requests（Pull Requestから書き込みトークンをワークフローに送信）** - 書き込み権限を持つ`GITHUB_TOKEN`の利用をフォークからのPull Requestに許可します。
-- **Send secrets to workflows from pull requests（Pull Requestからワークフローにシークレットを送信）** - すべてのシークレットをPull Requestから利用可能にします。
+プライベートリポジトリのフォークの利用に依存しているなら、ユーザがどのように`pull_request`イベントの際にワークフローを実行できるかを制御するポリシーを設定できます。 Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
new file mode 100644
index 0000000000..c51ca1a34a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
@@ -0,0 +1,3 @@
+```shell
+./run.sh --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md
index bf8cdb0082..756562f14d 100644
--- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md
+++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure.md
@@ -14,3 +14,6 @@
    - `config`スクリプトを実行してセルフホストランナーアプリケーションを設定し、{% data variables.product.prodname_actions %}に登録します。 `config`スクリプトには、登録先のURLと、リクエストを認証してもらうための自動的に生成された時間限定のあるトークンが必要です。
      - Windowsでは、`config`スクリプトはセルフホストランナーをサービスとしてインストールするかも聞いてきます。 LinuxとmacOSでは、ランナーの追加を終えた後にサービスをインストールできます。 詳しい情報については「[サービスとしてセルフホストランナーを構成する](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)」を参照してください。
    - セルフホストランナーアプリケーションを実行して、マシンを{% data variables.product.prodname_actions %}に接続します。
+{% ifversion fpt or ghec or ghes > 3.2 %}
+     - If you are setting up a cluster of runners, you can install another tool to automatically scale your runners.  For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/github-actions/sidebar-secret.md b/translations/ja-JP/data/reusables/github-actions/sidebar-secret.md
index 889315a304..50bf806141 100644
--- a/translations/ja-JP/data/reusables/github-actions/sidebar-secret.md
+++ b/translations/ja-JP/data/reusables/github-actions/sidebar-secret.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左サイドバーで [**Secrets**] をクリックします。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
index f078518c97..71244b328a 100644
--- a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
@@ -64,10 +64,10 @@ Ubuntu 18.04
 macOS Big Sur 11
 </td>
 <td>
-<code>macos-11</code>
+<code>macos-latest</code>もしくは<code>macos-11</code>
 </td>
 <td>
-The <code>macos-latest</code> label currently uses the macOS 10.15 runner image.
+The <code>macos-latest</code> label currently uses the macOS 11 runner image.
 </td>
 </tr>
 <tr>
@@ -75,7 +75,7 @@ The <code>macos-latest</code> label currently uses the macOS 10.15 runner image.
 macOS Catalina 10.15
 </td>
 <td>
-<code>macos-latest</code>もしくは<code>macos-10.15</code>
+<code>macos-10.15</code>
 </td>
 <td>
 </td>
@@ -83,6 +83,12 @@ macOS Catalina 10.15
 </tbody>
 </table>
 
+{% note %}
+
+**Note:** The `-latest` virtual environments are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor.
+
+{% endnote %}
+
 {% warning %}
 
 <b>Note:</b> Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support.
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/ja-JP/data/reusables/github-actions/workflow-dispatch-inputs.md
new file mode 100644
index 0000000000..bddb65defc
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/workflow-dispatch-inputs.md
@@ -0,0 +1,34 @@
+When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
+
+The triggered workflow receives the inputs in the `github.event.inputs` context. 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。
+
+```yaml
+on:
+  workflow_dispatch:
+    inputs:
+      logLevel:
+        description: 'Log level'
+        required: true
+        default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
+        type: choice
+        options:
+        - info
+        - warning
+        - debug {% endif %}
+      tags:
+        description: 'Test scenario tags'
+        required: false {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
+        type: boolean
+      environment:
+        description: 'Environment to run tests against'
+        type: environment
+        required: true {% endif %}
+
+jobs:
+  print-tag:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Print the input tag to STDOUT
+        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
+```
diff --git a/translations/ja-JP/data/reusables/organizations/billing-settings.md b/translations/ja-JP/data/reusables/organizations/billing-settings.md
index 78805492ce..feb35fd556 100644
--- a/translations/ja-JP/data/reusables/organizations/billing-settings.md
+++ b/translations/ja-JP/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
 {% data reusables.user_settings.access_settings %}
-2. 設定のサイドバーで、**Organizations**をクリックしてください。 ![サイドバーのOrganizationの設定](/assets/images/help/settings/settings-sidebar-organizations.png)
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% data reusables.profile.org_settings %}
-4. Organizationのオーナーは、左のサイドバーで**Billing & plans（支払とプラン）**をクリックしてください。 ![Organizationの設定サイドバーの支払とプラン](/assets/images/help/organizations/billing-settings.png)
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/ja-JP/data/reusables/organizations/billing_plans.md b/translations/ja-JP/data/reusables/organizations/billing_plans.md
index 04a951b633..f96c5bcea6 100644
--- a/translations/ja-JP/data/reusables/organizations/billing_plans.md
+++ b/translations/ja-JP/data/reusables/organizations/billing_plans.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+{% elsif ghes < 3.4 or ghae %}
 1. OrganizationのSettings（設定）サイドバーで、**Billing & plans（支払いとプラン）**をクリックしてください。 ![支払い設定](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/block_users.md b/translations/ja-JP/data/reusables/organizations/block_users.md
index 65309a24bc..10efc741f5 100644
--- a/translations/ja-JP/data/reusables/organizations/block_users.md
+++ b/translations/ja-JP/data/reusables/organizations/block_users.md
@@ -1 +1 @@
-1. OrganizationのSettings（設定）サイドバーで、**Blocked users（ブロックされたユーザ）**をクリックしてください。 ![Organizationの設定内のブロックされたユーザ](/assets/images/help/organizations/org-settings-block-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
diff --git a/translations/ja-JP/data/reusables/organizations/click-codespaces.md b/translations/ja-JP/data/reusables/organizations/click-codespaces.md
index 3c7ff3a042..2f409b474f 100644
--- a/translations/ja-JP/data/reusables/organizations/click-codespaces.md
+++ b/translations/ja-JP/data/reusables/organizations/click-codespaces.md
@@ -1 +1 @@
-1. 左のサイドバーで**Codespaces**をクリックしてください。 ![左のサイドバー内の"Codespaces"タブ](/assets/images/help/organizations/codespaces-sidebar-tab.png)
+1. In the left sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md
index 40a8b3338b..33a02edbbb 100644
--- a/translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のサイドバーで**{% data variables.product.prodname_github_apps %}**をクリックしてください。 ![{% data variables.product.prodname_github_apps %} settings](/assets/images/help/organizations/github-apps-settings-sidebar.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/member-privileges.md b/translations/ja-JP/data/reusables/organizations/member-privileges.md
index 5b3c173a35..cc34473d43 100644
--- a/translations/ja-JP/data/reusables/organizations/member-privileges.md
+++ b/translations/ja-JP/data/reusables/organizations/member-privileges.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
+{% elsif ghae or ghes < 3.4 %}
 4. 左のサイドバーで、**Member privileges（メンバーの権限）**をクリックしてください。 ![Org設定のメンバーの権限オプション](/assets/images/help/organizations/org-settings-member-privileges.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/moderation-settings.md b/translations/ja-JP/data/reusables/organizations/moderation-settings.md
index 94d3fde5d3..b79fd4132d 100644
--- a/translations/ja-JP/data/reusables/organizations/moderation-settings.md
+++ b/translations/ja-JP/data/reusables/organizations/moderation-settings.md
@@ -1 +1 @@
-1. 左サイドバーで [**Moderation settings**] をクリックします。 ![Moderation settings in organization's settings](/assets/images/help/organizations/org-settings-moderation-settings.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**
diff --git a/translations/ja-JP/data/reusables/organizations/oauth_app_access.md b/translations/ja-JP/data/reusables/organizations/oauth_app_access.md
index 390473e675..a2dc8773f5 100644
--- a/translations/ja-JP/data/reusables/organizations/oauth_app_access.md
+++ b/translations/ja-JP/data/reusables/organizations/oauth_app_access.md
@@ -1,3 +1 @@
-{% ifversion fpt or ghec %}
-  1. Settings（設定）サイドバーで、**Third-party access（サードパーティアクセス）**をクリックしてください。 ![左のサイドバーの{% data variables.product.prodname_oauth_app %}アクセスタブ](/assets/images/help/settings/settings-sidebar-third-party-access.png)
-{% endif %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
diff --git a/translations/ja-JP/data/reusables/organizations/org-settings-repository-roles.md b/translations/ja-JP/data/reusables/organizations/org-settings-repository-roles.md
index decd930cd5..937618670b 100644
--- a/translations/ja-JP/data/reusables/organizations/org-settings-repository-roles.md
+++ b/translations/ja-JP/data/reusables/organizations/org-settings-repository-roles.md
@@ -1 +1 @@
-4. 左のサイドバーで**Repository roles（リポジトリのロール）**をクリックしてください。 ![Organization設定のリポジトリロールタブ](/assets/images/help/organizations/org-settings-repository-roles.png)
+1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-label="The ID badge icon" %} Repository roles**.
diff --git a/translations/ja-JP/data/reusables/organizations/repository-defaults.md b/translations/ja-JP/data/reusables/organizations/repository-defaults.md
index 8707a22978..fd1dcf5bf0 100644
--- a/translations/ja-JP/data/reusables/organizations/repository-defaults.md
+++ b/translations/ja-JP/data/reusables/organizations/repository-defaults.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のサイドバーで**Repository defaults（リポジトリのデフォルト）**をクリックしてください。 ![リポジトリのデフォルトタブ](/assets/images/help/organizations/repo-defaults-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/repository-labels.md b/translations/ja-JP/data/reusables/organizations/repository-labels.md
index 1909ac824b..eff89977d3 100644
--- a/translations/ja-JP/data/reusables/organizations/repository-labels.md
+++ b/translations/ja-JP/data/reusables/organizations/repository-labels.md
@@ -1 +1 @@
-1. 左のサイドバーで、**Repository labels（リポジトリのラベル）**をクリックしてください。 ![リポジトリのラベルタブ](/assets/images/help/organizations/repo-labels-tab.png)
+1. 左のサイドバーで、**Repository labels（リポジトリのラベル）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/organizations/security-and-analysis.md b/translations/ja-JP/data/reusables/organizations/security-and-analysis.md
index 6654b5dab1..7bc9d0b084 100644
--- a/translations/ja-JP/data/reusables/organizations/security-and-analysis.md
+++ b/translations/ja-JP/data/reusables/organizations/security-and-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のサイドバーで、**Security & analysis（セキュリティと分析）**をクリックしてください。 ![Organization設定の"セキュリティと分析"タブ](/assets/images/help/organizations/org-settings-security-and-analysis.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/security.md b/translations/ja-JP/data/reusables/organizations/security.md
index 042888e189..da9d7adcfb 100644
--- a/translations/ja-JP/data/reusables/organizations/security.md
+++ b/translations/ja-JP/data/reusables/organizations/security.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
+{% else  %}
 1. 左のサイドバーで**Organization security（Organizationのセキュリティ）**をクリックしてください。
 
  ![Organizationのセキュリティ設定](/assets/images/help/organizations/org-security-settings-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/teams_sidebar.md b/translations/ja-JP/data/reusables/organizations/teams_sidebar.md
index 87825253c5..3085acc62e 100644
--- a/translations/ja-JP/data/reusables/organizations/teams_sidebar.md
+++ b/translations/ja-JP/data/reusables/organizations/teams_sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
 1. Settings（設定）サイドバーで、**Teams**をクリックしてください。 ![Organizationの設定サイドバー内のTeamsタブ](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/verified-domains.md b/translations/ja-JP/data/reusables/organizations/verified-domains.md
index 395fd3b5c8..de48abaea3 100644
--- a/translations/ja-JP/data/reusables/organizations/verified-domains.md
+++ b/translations/ja-JP/data/reusables/organizations/verified-domains.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のサイドバーで**Verified & approved domains（検証済み及び承認済みドメイン）**をクリックしてください。 !["検証済み及び承認済みドメイン"タブ](/assets/images/help/organizations/verified-domains-button.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/pages/sidebar-pages.md b/translations/ja-JP/data/reusables/pages/sidebar-pages.md
index 145af43bf9..ca25553251 100644
--- a/translations/ja-JP/data/reusables/pages/sidebar-pages.md
+++ b/translations/ja-JP/data/reusables/pages/sidebar-pages.md
@@ -1,3 +1,5 @@
-{% ifversion fpt or ghes > 3.1 or ghec %}
+{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
+1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
+{% else %}
 1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![左のサイドバーのPageタブ](/assets/images/help/pages/pages-tab.png)
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/profile/org_member_privileges.md b/translations/ja-JP/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..c0462ae849
--- /dev/null
+++ b/translations/ja-JP/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1 @@
+3. Under "Access", click **Member privileges**. ![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png) 
diff --git a/translations/ja-JP/data/reusables/reminders/scheduled-reminders.md b/translations/ja-JP/data/reusables/reminders/scheduled-reminders.md
index e7c4588a50..b45b072c3c 100644
--- a/translations/ja-JP/data/reusables/reminders/scheduled-reminders.md
+++ b/translations/ja-JP/data/reusables/reminders/scheduled-reminders.md
@@ -1 +1 @@
-1. 左のサイドバーで**Scheduled reminders（スケジュールされたリマインダー）**をクリックしてください。
+1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-label="The clock icon" %} Scheduled reminders**.
diff --git a/translations/ja-JP/data/reusables/repositories/click-collaborators-teams.md b/translations/ja-JP/data/reusables/repositories/click-collaborators-teams.md
new file mode 100644
index 0000000000..300fea61ad
--- /dev/null
+++ b/translations/ja-JP/data/reusables/repositories/click-collaborators-teams.md
@@ -0,0 +1 @@
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Collaborators & teams**.
diff --git a/translations/ja-JP/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/ja-JP/data/reusables/repositories/navigate-to-security-and-analysis.md
index 59990e5634..ba4d234a1a 100644
--- a/translations/ja-JP/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/ja-JP/data/reusables/repositories/navigate-to-security-and-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のサイドバーで、**Security & analysis（セキュリティと分析）**をクリックしてください。 ![リポジトリ設定の"セキュリティと分析"タブ](/assets/images/help/repository/security-and-analysis-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/repository-branches.md b/translations/ja-JP/data/reusables/repositories/repository-branches.md
index 2bd51a9091..e1f19bb092 100644
--- a/translations/ja-JP/data/reusables/repositories/repository-branches.md
+++ b/translations/ja-JP/data/reusables/repositories/repository-branches.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
+{% elsif ghes < 3.4 or ghae %}
 1. 左のメニューで**Branches（ブランチ）**をクリックしてください。 ![リポジトリオプションのサブメニュー](/assets/images/help/repository/repository-options-branch.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-moderation-reported-content.md b/translations/ja-JP/data/reusables/repositories/sidebar-moderation-reported-content.md
index 1f57b1a3b1..6d184ae816 100644
--- a/translations/ja-JP/data/reusables/repositories/sidebar-moderation-reported-content.md
+++ b/translations/ja-JP/data/reusables/repositories/sidebar-moderation-reported-content.md
@@ -1 +1 @@
-1. 左のサイドバーで**Reported content（レポートされた内容）**をクリックしてください。 ![リポジトリ設定サイドバーの"レポートされた内容"](/assets/images/help/repository/repo-settings-reported-content.png)
+1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Reported content**.
diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-notifications.md b/translations/ja-JP/data/reusables/repositories/sidebar-notifications.md
index 22c2a69c2f..116a737cd4 100644
--- a/translations/ja-JP/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/ja-JP/data/reusables/repositories/sidebar-notifications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
 1. **Notifications（通知）**をクリックしてください。 ![サイドバーの通知ボタン](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 398e34532b..626e27e748 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -155,6 +155,8 @@ Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key
 PyPI | PyPI API Token | pypi_api_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae %}
+Segment | Segment Public API Token | segment_public_api_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
diff --git a/translations/ja-JP/data/reusables/security/compliance-report-list.md b/translations/ja-JP/data/reusables/security/compliance-report-list.md
new file mode 100644
index 0000000000..7bce73219d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/security/compliance-report-list.md
@@ -0,0 +1,4 @@
+- SOC 1, Type 2
+- SOC 2, Type 2
+- Cloud Security Alliance CAIQ self-assessment (CSA CAIQ)
+- {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/security/compliance-report-screenshot.md b/translations/ja-JP/data/reusables/security/compliance-report-screenshot.md
new file mode 100644
index 0000000000..984c8d6d8b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/security/compliance-report-screenshot.md
@@ -0,0 +1 @@
+![Screenshot of download button to the right of a compliance report](/assets/images/help/settings/compliance-report-download.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/sponsors-only-repos.md b/translations/ja-JP/data/reusables/sponsors/sponsors-only-repos.md
new file mode 100644
index 0000000000..0361572c97
--- /dev/null
+++ b/translations/ja-JP/data/reusables/sponsors/sponsors-only-repos.md
@@ -0,0 +1 @@
+You can give all sponsors in a tier access to a private repository by adding the repository to the tier.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/tier-details.md b/translations/ja-JP/data/reusables/sponsors/tier-details.md
index f63e5c6baa..2f76e3cdd2 100644
--- a/translations/ja-JP/data/reusables/sponsors/tier-details.md
+++ b/translations/ja-JP/data/reusables/sponsors/tier-details.md
@@ -3,10 +3,11 @@ You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for spon
 各層の謝礼をカスタマイズできます。 たとえば、層の謝礼には以下のようなものがあるでしょう:
 - 新バージョンへの早期アクセス
 - README内にロゴもしくは名前
-- プライベートリポジトリへのアクセス
 - 週次のニュースレターの更新
 - スポンサーが喜ぶその他の謝礼
 
+{% data reusables.sponsors.sponsors-only-repos %} For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)."
+
 You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email.
 
 層を公開すると、その層の金額は編集できなくなります。 その代わりに、その層を止めて新しい層を作成できます。 終了した層の既存のスポンサーは、スポンサーシップの層を変更するか、スポンサーシップをキャンセルするか、1回のスポンサーシップの期間が終了するまで、そのまま残ります。
diff --git a/translations/ja-JP/data/reusables/user-settings/oauth_apps.md b/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
index 5fcccdf79b..9bae66e092 100644
--- a/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
+++ b/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
@@ -1 +1 @@
-1. ひだりのサイドバーで**OAuth Apps**をクリックしてください。 ![OAuth Appsセクション](/assets/images/help/settings/developer-settings-oauth-apps.png)
+1. 左のサイドバーで**{% data variables.product.prodname_oauth_apps %}**をクリックしてください。 ![OAuth Appsセクション](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/access_applications.md b/translations/ja-JP/data/reusables/user_settings/access_applications.md
index 1706276b05..53d3f045e8 100644
--- a/translations/ja-JP/data/reusables/user_settings/access_applications.md
+++ b/translations/ja-JP/data/reusables/user_settings/access_applications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
 1. 左のサイドバーで、**Applications（アプリケーション）** をクリックしてください。 ![アプリケーションタブ](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/accessibility_settings.md b/translations/ja-JP/data/reusables/user_settings/accessibility_settings.md
index b23486a3ff..2c9e37e2f4 100644
--- a/translations/ja-JP/data/reusables/user_settings/accessibility_settings.md
+++ b/translations/ja-JP/data/reusables/user_settings/accessibility_settings.md
@@ -1 +1 @@
-1. In the navigation on the left hand side, click the **Accessibility** link. ![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)
+1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**.
diff --git a/translations/ja-JP/data/reusables/user_settings/account_settings.md b/translations/ja-JP/data/reusables/user_settings/account_settings.md
index fa5f55fe00..036a5cc2cd 100644
--- a/translations/ja-JP/data/reusables/user_settings/account_settings.md
+++ b/translations/ja-JP/data/reusables/user_settings/account_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+1. 左サイドバーで [**{% octicon "gear" aria-label="The gear icon" %} Account**] をクリックします。
+{% else %}
 1. 左のサイドバーで**Account（アカウント）**をクリックしてください。 ![アカウント設定メニューオプション](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/appearance-settings.md b/translations/ja-JP/data/reusables/user_settings/appearance-settings.md
index d764df6b85..04aebed9f1 100644
--- a/translations/ja-JP/data/reusables/user_settings/appearance-settings.md
+++ b/translations/ja-JP/data/reusables/user_settings/appearance-settings.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
 1. [User settings] サイドバーで、[**Appearance**] をクリックします。
 
-   ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
+   ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/billing_plans.md b/translations/ja-JP/data/reusables/user_settings/billing_plans.md
index e0308860fb..333102205b 100644
--- a/translations/ja-JP/data/reusables/user_settings/billing_plans.md
+++ b/translations/ja-JP/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. ユーザ設定サイドバーで**Billing & plans（支払いプラン）**をクリックしてください。 ![支払いプランの設定](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/ja-JP/data/reusables/user_settings/blocked_users.md b/translations/ja-JP/data/reusables/user_settings/blocked_users.md
index 7d85f88d25..b7ba502dca 100644
--- a/translations/ja-JP/data/reusables/user_settings/blocked_users.md
+++ b/translations/ja-JP/data/reusables/user_settings/blocked_users.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Blocked users** under **Moderation settings**. ![ブロックされたユーザタブ](/assets/images/help/settings/settings-sidebar-blocked-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**.
diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
index fa52e0f572..5aa532885e 100644
--- a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
+++ b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
@@ -1 +1 @@
-1. 左のサイドバーで**Codespaces**をクリックしてください。 ![ユーザ設定サイドバーのCodespacesタブ](/assets/images/help/settings/codespaces-tab.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/ja-JP/data/reusables/user_settings/developer_settings.md b/translations/ja-JP/data/reusables/user_settings/developer_settings.md
index ea7640e76f..216fdc8ac3 100644
--- a/translations/ja-JP/data/reusables/user_settings/developer_settings.md
+++ b/translations/ja-JP/data/reusables/user_settings/developer_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %}
 1. 左サイドバーで [**Developer settings**] をクリックします。 ![開発者設定](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/emails.md b/translations/ja-JP/data/reusables/user_settings/emails.md
index 04187ad5c8..e4d7b00089 100644
--- a/translations/ja-JP/data/reusables/user_settings/emails.md
+++ b/translations/ja-JP/data/reusables/user_settings/emails.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
 1. 左のサイドバーで**Emails（メール）**をクリックしてください。 ![メールタブ](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/organizations.md b/translations/ja-JP/data/reusables/user_settings/organizations.md
index c4db6fd907..e5585885ab 100644
--- a/translations/ja-JP/data/reusables/user_settings/organizations.md
+++ b/translations/ja-JP/data/reusables/user_settings/organizations.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
 1. ユーザ設定サイドバーで**Organizations**をクリックしてください。 ![Organization用のユーザ設定](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/repo-tab.md b/translations/ja-JP/data/reusables/user_settings/repo-tab.md
index e111b01917..482857ffbd 100644
--- a/translations/ja-JP/data/reusables/user_settings/repo-tab.md
+++ b/translations/ja-JP/data/reusables/user_settings/repo-tab.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 1. 左のサイドバーで [**Repositories**] をクリックします。 ![[Repositories] タブ](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/saved_replies.md b/translations/ja-JP/data/reusables/user_settings/saved_replies.md
index b705a3d703..bb7fe59782 100644
--- a/translations/ja-JP/data/reusables/user_settings/saved_replies.md
+++ b/translations/ja-JP/data/reusables/user_settings/saved_replies.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
 1. 左のサイドバーで**Saved replies（返信テンプレート）**をクリックしてください。 ![返信テンプレートタブ](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/security-analysis.md b/translations/ja-JP/data/reusables/user_settings/security-analysis.md
index dbf88ee9b5..a7ce0cd79d 100644
--- a/translations/ja-JP/data/reusables/user_settings/security-analysis.md
+++ b/translations/ja-JP/data/reusables/user_settings/security-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
 1. 左のサイドバーで、**Security & analysis（セキュリティと分析）**をクリックしてください。 ![セキュリティと分析の設定](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/security.md b/translations/ja-JP/data/reusables/user_settings/security.md
index 21ba73b08e..15173cb444 100644
--- a/translations/ja-JP/data/reusables/user_settings/security.md
+++ b/translations/ja-JP/data/reusables/user_settings/security.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
 1. 左のサイドバーで**Account security（アカウントのセキュリティ）**をクリックしてください。 ![ユーザアカウントのセキュリティ設定](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/ssh.md b/translations/ja-JP/data/reusables/user_settings/ssh.md
index b6f40ed876..18ac525019 100644
--- a/translations/ja-JP/data/reusables/user_settings/ssh.md
+++ b/translations/ja-JP/data/reusables/user_settings/ssh.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
 1. ユーザ設定サイドバーで**SSH and GPG keys（SSH及びGPGキー）**をクリックしてください。 ![認証キー](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 89103a361d..f1ed26a4ea 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -13,6 +13,7 @@ header:
     ghes_release_notes_upgrade_patch_only: '📣 これはEnterprise Serverの<a href="#{{ latestPatch }}">最新のパッチリリース</a>ではありません。'
     ghes_release_notes_upgrade_release_only: '📣 これはEnterprise Serverの<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新リリース</a>ではありません。'
     ghes_release_notes_upgrade_patch_and_release: '📣 これはこのリリースシリーズの<a href="#{{ latestPatch }}">最新パッチリリース</a>ではなく、これはEnterprise Serverの<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新リリース</a>ではありません。'
+  sign_up_cta: サインアップ
 picker:
   language_picker_default_text: Choose a language
   product_picker_default_text: All products
@@ -37,11 +38,12 @@ toc:
   guides: ガイド
   whats_new: 更新情報
   videos: 動画
+  all_changelogs: All changelog posts
 pages:
   article_version: 'Article version'
   miniToc: 'ここには以下の内容があります:'
   contributor_callout: この記事は、次の人によってコントリビュートされ、管理されています。
-  all_enterprise_releases: All Enterprise releases
+  all_enterprise_releases: All Enterprise Server releases
 errors:
   oops: 問題が発生しています。
   something_went_wrong: 何か問題が生じています。
@@ -159,10 +161,12 @@ product_landing:
   release_notes_for: リリースノート
   upgrade_from: アップグレード元
   browse_all_docs: すべてのドキュメントの参照
+  browse_all: Browse all
+  docs: ドキュメント
   explore_release_notes: リリースノートを調べる
+  view: 全てを表示
 product_guides:
-  start: 開始
-  start_path: 開始パス
+  start_path: Start learning path
   learning_paths: '{{ productMap[currentProduct].name }}の学習パス'
   learning_paths_desc: 学習パスは、特定の課題をマスターするのに役立つガイド集です。
   guides: '{{ productMap[currentProduct].name }}のガイド'
diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index a2925060c5..7c8e1ac6c3 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -121,6 +121,7 @@ translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learni
 translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
+translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
 translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,broken liquid tags
 translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,broken liquid tags
@@ -131,9 +132,7 @@ translations/zh-CN/content/get-started/quickstart/github-flow.md,broken liquid t
 translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-errors.md,broken liquid tags
 translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags
 translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
-translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,broken liquid tags
-translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md,Listed in localization-support#489
 translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index e213c3103a..b94241f02d 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -93,6 +93,7 @@ translations/es-ES/content/billing/managing-billing-for-github-advanced-security
 translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,Listed in localization-support#489
 translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,broken liquid tags
 translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,Listed in localization-support#489
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
@@ -100,7 +101,6 @@ translations/es-ES/content/code-security/code-scanning/automatically-scanning-yo
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,Listed in localization-support#489
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,Listed in localization-support#489
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,Listed in localization-support#489
@@ -180,6 +180,7 @@ translations/es-ES/content/education/manage-coursework-with-github-classroom/tea
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,Listed in localization-support#489
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,Listed in localization-support#489
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,Listed in localization-support#489
+translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,Listed in localization-support#489
 translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,broken liquid tags
 translations/es-ES/content/get-started/quickstart/be-social.md,Listed in localization-support#489
@@ -196,7 +197,6 @@ translations/es-ES/content/get-started/using-github/github-command-palette.md,Li
 translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,Listed in localization-support#489
 translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,Listed in localization-support#489
 translations/es-ES/content/github/copilot/index.md,Listed in localization-support#489
-translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/es-ES/content/github/index.md,Listed in localization-support#489
 translations/es-ES/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,Listed in localization-support#489
 translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md,Listed in localization-support#489
@@ -209,8 +209,6 @@ translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-iss
 translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,Listed in localization-support#489
 translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,Listed in localization-support#489
 translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,Listed in localization-support#489
-translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
 translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,Listed in localization-support#489
 translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,broken liquid tags
 translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,Listed in localization-support#489
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 7dcbab7def..1cac04a053 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -80,6 +80,7 @@ translations/ja-JP/content/billing/managing-billing-for-github-advanced-security
 translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md,broken liquid tags
 translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
@@ -138,6 +139,7 @@ translations/ja-JP/content/education/manage-coursework-with-github-classroom/int
 translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
 translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,broken liquid tags
 translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
+translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/ja-JP/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
 translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,Listed in localization-support#489
 translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,parsing error
@@ -145,10 +147,8 @@ translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-setti
 translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
 translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags
 translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
-translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags
 translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489
-translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
 translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
 translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
 translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md,broken liquid tags
@@ -195,6 +195,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-1/12.yml,broken liquid
 translations/ja-JP/data/release-notes/enterprise-server/3-1/13.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/3-1/14.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/3-1/15.yml,broken liquid tags
+translations/ja-JP/data/release-notes/enterprise-server/3-1/16.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/3-1/2.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/3-1/3.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/3-1/4.yml,broken liquid tags
diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv
index a3dd42b049..49d8776218 100644
--- a/translations/log/pt-resets.csv
+++ b/translations/log/pt-resets.csv
@@ -16,20 +16,19 @@ translations/pt-BR/content/admin/user-management/managing-users-in-your-enterpri
 translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
 translations/pt-BR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489
 translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags
 translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags
 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
+translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
 translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
-translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
 translations/pt-BR/content/github/index.md,Listed in localization-support#489
-translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
-translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,parsing error
+translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,parsing error
 translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
 translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
 translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index f665ac9e45..6f18634301 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
-product: '{% ifversion fpt %}{% data reusables.gated-features.user-repo-collaborators %}{% endif %}'
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 1cb296c67d..8a53be2b9a 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -9,7 +9,6 @@ redirect_from:
   - /articles/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
-product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -22,6 +21,10 @@ shortTitle: Remover-se
 ---
 
 {% data reusables.user_settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 2. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
 3. Clique em **Leave** (Sair) ao lado do repositório do qual deseja sair. ![Botão Leave (Sair)](/assets/images/help/repository/repo-leave.png)
 4. Leia o aviso com atenção, depois clique em "I understand, leave this repository" (Eu compreendo, sair deste repositório). ![Caixa de diálogo avisando você para sair](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
index 443bf9a213..04f6fda28c 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -13,12 +13,12 @@ shortTitle: Integrar o Jira com projetos
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
-3. Na barra lateral esquerda, clique em **{% data variables.product.prodname_oauth_apps %}**. ![{% data variables.product.prodname_oauth_apps %} aba na barra lateral esquerda](/assets/images/help/settings/developer-settings-oauth-apps.png)
-3. Clique em **Register a new application** (Registrar novo aplicativo).
-4. Em **Application name** (Nome do aplicativo), digite "Jira".
-5. Em **Homepage URL** (URL da página inicial), digite a URL completa da sua instância do JIRA.
-6. Em **Authorization callback URL** (URL de revogação de autorização), digite a URL completa da sua instância do JIRA.
-7. Clique em **Register application** (Registrar aplicativo). ![Botão Register application (registrar aplicativo)](/assets/images/help/oauth/register-application-button.png)
+{% data reusables.user-settings.oauth_apps %}
+1. Clique em **Register a new application** (Registrar novo aplicativo).
+2. Em **Application name** (Nome do aplicativo), digite "Jira".
+3. Em **Homepage URL** (URL da página inicial), digite a URL completa da sua instância do JIRA.
+4. Em **Authorization callback URL** (URL de revogação de autorização), digite a URL completa da sua instância do JIRA.
+5. Clique em **Register application** (Registrar aplicativo). ![Botão Register application (registrar aplicativo)](/assets/images/help/oauth/register-application-button.png)
 8. Em **Aplicativos do desenvolvedor**, anote os valores "Client ID" (ID do cliente) e "Client Secret" (Chave secreta do cliente). ![Client ID (ID do cliente) e Client Secret (Chave secreta do cliente)](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 7c2482dbaa..474fd1449c 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,5 +14,5 @@ shortTitle: Gerenciando o tamanho da sua aba
 Se você considerar que a indentação em abas no código interpretado em {% data variables.product.product_name %} demanda muito tempo, ou muito pouco espaço, você poderá alterar isto nas suas configurações.
 
 {% data reusables.user_settings.access_settings %}
-1. Na barra lateral de configurações do usuário, clique em **Aparência**. ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png)
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 2. Em "Preferência do tamanho da aba", selecione o menu suspenso e escolha sua preferência. ![Botão de preferência do tamanho da aba](/assets/images/help/settings/tab-size-preference.png)
diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index db7084d84d..d491d5c4f1 100644
--- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 4
 
 ## Sobre sintaxe YAML para o {% data variables.product.prodname_actions %}
 
-Ações Docker e JavaScript requerem um arquivo de metadados. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. Os dados no arquivo de metadados definem as entradas, as saídas e o ponto de entrada principal para sua ação.
+All actions require a metadata file. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
 
 Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que é YAML, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index f3e9de4a40..8572081125 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -217,6 +217,10 @@ Por exemplo:
 curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
 ```
 
+### Adicionando configurações de permissões
+
+{% data reusables.actions.oidc-permissions-token %}
+
 ## Atualizando seus fluxos de trabalho para o OIDC
 
 Agora você pode atualizar seus fluxos de trabalho do YAML para usar tokens de acesso do OIDC em vez de segredos. Os provedores de nuvem populares publicaram suas ações de login oficiais que facilitam o seu início de sessão com o OIDC. Para obter mais informações sobre a atualização dos seus fluxos de trabalho, consulte os guias específicos da nuvem listados abaixo em "[Habilitando o OpenID Connect para o seu provedor de nuvem](#enabling-openid-connect-for-your-cloud-provider)".
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index dcb4212a84..690364f69f 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -56,14 +56,7 @@ Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alt
 
 ### Adicionando configurações de permissões
 
-O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Solicitando o token de acesso
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 7aeb44c5ac..192c6cee5a 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -50,14 +50,7 @@ Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alt
 
 ### Adicionando configurações de permissões
 
-O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Solicitando o token de acesso
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index e73105805e..301411f986 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -37,14 +37,7 @@ Se seu provedor de nuvem ainda não oferece uma ação oficial, você pode atual
 
 ### Adicionando configurações de permissões
 
-O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Usando ações oficiais
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index 31548ef32a..93336f215c 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -49,14 +49,7 @@ Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alt
 
 ### Adicionando configurações de permissões
 
-O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Solicitando o token de acesso
 
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 7c08d9be46..60fcaa150a 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -54,14 +54,7 @@ Este exemplo demonstra como usar o OIDC com a ação oficial para solicitar um s
 
 ### Adicionando configurações de permissões
 
-O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Solicitando o token de acesso
 
diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md
index c32838caee..be178403ba 100644
--- a/translations/pt-BR/content/actions/index.md
+++ b/translations/pt-BR/content/actions/index.md
@@ -32,7 +32,6 @@ featuredLinks:
     - title: GitHub Actions in action – Karan MV
       href: 'https://www.youtube-nocookie.com/embed/4SWO0Pc76CU'
   videosHeading: GitHub Universe 2021 videos
-examples_source: data/product-examples/actions/code-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
 redirect_from:
   - /articles/automating-your-workflow-with-github-actions
diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index b0216a1b13..a949fddb04 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -18,16 +18,23 @@ shortTitle: Cobrança do fluxo de trabalho & limites
 
 ## Sobre a cobrança do {% data variables.product.prodname_actions %}
 
+{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% else %}
-O uso do GitHub Actions é gratuito para {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados.
+GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 {% endif %}
 
+
+{% ifversion fpt or ghec %}
+
 ## Disponibilidade
 
 {% data variables.product.prodname_actions %} está disponível em todos os produtos de {% data variables.product.prodname_dotcom %}, mas {% data variables.product.prodname_actions %} não está disponível para repositórios privados pertencentes a contas usando planos legados por repositório. {% data reusables.gated-features.more-info %}
 
+{% endif %}
+
 ## Limites de uso
 
 {% ifversion fpt or ghec %}
diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
index 57b80642df..b7825a578f 100644
--- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
@@ -80,20 +80,20 @@ Para obter informações sobre quais os pontos de extremidade da API de {% data
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão. As pessoas com permissões de administrador para uma empresa, organização ou repositório de {% ifversion not ghes %}{% else %}organização ou repositório{% endif %} pode definir as permissões padrão como permissivas ou restritas. Para informações sobre como definir as permissões padrão para o `GITHUB_TOKEN` para a sua empresa, organização ou repositório, consulte "[Aplicando políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise), "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization), ou "[Gerenciando configurações do {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
 
-| Escopo              | Acesso padrão<br>(permissivo) | Acesso padrão<br>(restrito) | Acesso máximo<br>por repositórios bifurcados |
-| ------------------- | ----------------------------------- | --------------------------------- | -------------------------------------------------- |
-| ações               | leitura/gravação                    | nenhum                            | leitura                                            |
-| Verificações        | leitura/gravação                    | nenhum                            | leitura                                            |
-| Conteúdo            | leitura/gravação                    | leitura                           | leitura                                            |
-| Implantações        | leitura/gravação                    | nenhum                            | leitura                                            |
-| id-token            | leitura/gravação                    | nenhum                            | leitura                                            |
-| Problemas           | leitura/gravação                    | nenhum                            | leitura                                            |
-| metadados           | leitura                             | leitura                           | leitura                                            |
-| pacotes             | leitura/gravação                    | nenhum                            | leitura                                            |
-| pull-requests       | leitura/gravação                    | nenhum                            | leitura                                            |
-| repository-projects | leitura/gravação                    | nenhum                            | leitura                                            |
-| security-events     | leitura/gravação                    | nenhum                            | leitura                                            |
-| Status              | leitura/gravação                    | nenhum                            | leitura                                            |
+| Escopo       | Acesso padrão<br>(permissivo) | Acesso padrão<br>(restrito) | Acesso máximo<br>por repositórios bifurcados |
+| ------------ | ----------------------------------- | --------------------------------- | -------------------------------------------------- |
+| ações        | leitura/gravação                    | nenhum                            | leitura                                            |
+| Verificações | leitura/gravação                    | nenhum                            | leitura                                            |
+| Conteúdo     | leitura/gravação                    | leitura                           | leitura                                            |
+| Implantações | leitura/gravação                    | nenhum                            | leitura                                            |
+| id-token     | leitura/gravação                    | nenhum                            | leitura                                            |
+| Problemas    | leitura/gravação                    | nenhum                            | leitura                                            |
+| metadados    | leitura                             | leitura                           | leitura                                            |
+| pacotes      | leitura/gravação                    | nenhum                            | leitura                                            |
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
+| pages         | read/write  | none | read |
+{%- endif %}
+| pull-requests | read/write  | none | read | | repository-projects | read/write | none | read | | security-events     | read/write | none | read | | statuses      | read/write  | none | read |
 {% else %}
 | Escopo              | Tipo de acesso   | Acesso pelos repositórios bifurcados |
 | ------------------- | ---------------- | ------------------------------------ |
diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
index 0995478b74..65f2a399db 100644
--- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
@@ -354,3 +354,50 @@ Os segredos são limitados a 64 kB. Para usar segredos maiores que 64 kB, você
           run: cat $HOME/secrets/my_secret.json
   ```
 {% endraw %}
+
+
+## Storing Base64 binary blobs as secrets
+
+You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+
+{% note %}
+
+**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+
+{% endnote %}
+
+1. Use `base64` to encode your file into a Base64 string. Por exemplo:
+
+   ```
+   $ base64 -i cert.der -o cert.base64
+   ```
+
+1. Create a secret that contains the Base64 string. Por exemplo:
+
+   ```
+   $ gh secret set CERTIFICATE_BASE64 < cert.base64
+   ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
+   ```
+
+1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  Por exemplo:
+
+   ```yaml
+   name: Retrieve Base64 secret
+   on:
+     push:
+       branches: [ octo-branch ]
+   jobs:
+     decode-secret:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: actions/checkout@v2
+         - name: Retrieve the secret and decode it to a file
+           env:
+             {% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
+           run: |
+             echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
+         - name: Show certificate information
+           run: |
+             openssl x509 -in cert.der -inform DER -text -noout
+   ```
+
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index a7e7486f2f..d0a7d33cce 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -973,7 +973,7 @@ Par aobte rmais informações sobre branch, tag e sintaxe de filtro do caminho,
 | `'**'`                                                  | Corresponde a todos os nomes de branches e tags. Esse é o comportamento padrão quando você não usa um filtro de `branches` ou `tags`.                                               | `all/the/branches`<br/><br/>`every/tag`                                                                   |
 | `'*feature'`                                            | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas.                                                                                 | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
 | `v2*`                                                   | Corresponde aos nomes de branches e tags que iniciam com `v2`.                                                                                                                      | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
-| `v[12].[0-9]+.[0-9]+`                                   | Corresponde a todas as tags de versão de branch semântica com a versão principal 1 ou 2                                                                                             | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
+| `v[12].[0-9]+.[0-9]+`                                   | Corresponde a todas as tags de versão de branch semântica com a versão principal 1 ou 2.                                                                                            | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
 ### Padrões para corresponder a caminhos de arquivos
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
index e9a382dceb..5cee49be71 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -38,6 +38,8 @@ Você pode gerar uma solicitação de assinatura de certificado (CSR, Certificat
 
 ## Fazer upload de um certificado TLS personalizado
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
@@ -67,6 +69,8 @@ Você também pode usar o utilitário de linha de comando `ghe-ssl-acme` na {% d
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index dca3940ae1..8d7334316d 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -137,5 +137,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 Você pode usar estas opções adicionais com o comando `ghe-restore`:
-- O sinalizador `-c` substitui as configurações, os certificados e os dados de licença no host de destino, mesmo que já configurado. Omita esse sinalizador se você estiver configurando uma instância de preparo para fins de teste e se quiser manter a configuração no destino. Para obter mais informações, consulte a seção "Usar comandos de backup e restauração" do [README do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- O sinalizador `-c` substitui as configurações, os certificados e os dados de licença no host de destino, mesmo que já configurado. Omita esse sinalizador se você estiver configurando uma instância de preparo para fins de teste e se quiser manter a configuração no destino. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - O sinalizador `-s` permite selecionar outro instantâneo de backup.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index 522ab7bf3b..c25ba80f49 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -74,7 +74,7 @@ Os proprietários das empresas podem configurar e-mails para notificações.
 
 4. Se houver falha no teste, consulte a [solução de problemas das suas configurações de e-mail](#troubleshooting-email-delivery).
 5. Quando o teste for concluído com êxito, clique em **Save settings** (Salvar configurações) na parte inferior da página. ![Botão Save settings (Salvar configurações)](/assets/images/enterprise/management-console/save-settings.png)
-6. Aguarde a conclusão da execução de suas configurações. ![Configurar a instância](/assets/images/enterprise/management-console/configuration-run.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 ## Configurar DNS e firewall para o recebimento de e-mails
 
diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index f21c4d29ae..6cda083d1e 100644
--- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -52,9 +52,11 @@ Se você usa ações do contêiner do Docker ou contêineres de serviço nos seu
 
 Se estas configurações não estiverem definidas corretamente, você poderá receber erros como `Recurso movido inesperadamente para https://<IP_ADDRESS>` ao definir ou mudar a configuração de {% data variables.product.prodname_actions %}.
 
-## Os executores que não se conectam a {% data variables.product.prodname_ghe_server %} depois de mudar o hostname
+## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
 
-Se você alterar o nome do host de {% data variables.product.product_location %}, os executores auto-hospedados não poderão conectar-se ao host antigo e não executarão nenhum trabalho.
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
 
 Você precisará atualizar a configuração dos seus executores auto-hospedados para usar o novo nome de host para {% data variables.product.product_location %}. Cada executor auto-hospedado exigirá um dos seguintes procedimentos:
 
diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index f2862995fb..22229c4087 100644
--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -15,8 +15,6 @@ redirect_from:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
-
 ## Sobre o logon único SAML para contas corporativas
 
 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md
index eb6fba1ca5..c11ee43ec6 100644
--- a/translations/pt-BR/content/admin/index.md
+++ b/translations/pt-BR/content/admin/index.md
@@ -97,12 +97,14 @@ featuredLinks:
     - '{% ifversion ghes %}/admin/installation{% endif %}'
     - '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
     - '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
     - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
     - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
+    - /admin/configuration/configuring-github-connect/managing-github-connect
     - /admin/enterprise-support/about-github-enterprise-support
   videos:
     - title: GitHub in the Enterprise – Maya Ross
diff --git a/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
new file mode 100644
index 0000000000..94a59a4a6f
--- /dev/null
+++ b/translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your enterprise
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Enterprise owners can access compliance reports for the enterprise.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Leia mais
+
+- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
diff --git a/translations/pt-BR/content/admin/overview/index.md b/translations/pt-BR/content/admin/overview/index.md
index 489d891e0e..1bbb42b666 100644
--- a/translations/pt-BR/content/admin/overview/index.md
+++ b/translations/pt-BR/content/admin/overview/index.md
@@ -15,6 +15,7 @@ children:
   - /system-overview
   - /about-the-github-enterprise-api
   - /creating-an-enterprise-account
+  - /accessing-compliance-reports-for-your-enterprise
 ---
 
 Para obter mais informações ou comprar o {% data variables.product.prodname_enterprise %}, consulte [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 806b10af2e..75aaf2ce9f 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -146,9 +146,8 @@ A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no
 {% data reusables.organizations.delete-ssh-ca %}
 
 {% ifversion ghec or ghae %}
-
 ## Leia mais
 
-- "[Sobre a identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
-
+- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
 {% endif %}
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 59292b6eb3..3cb8e26c18 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -81,27 +81,23 @@ As seguintes variáveis estão sempre disponíveis no ambiente de do hook pre-re
 
 A variável `$GITHUB_VIA` está disponível no ambiente de pre-receive quando a atualização de ref que aciona o hook por meio da interface da web ou da API para {% data variables.product.prodname_ghe_server %}. O valor descreve a ação que atualizou o ref.
 
-| Valor                      | Ação                                                                                                                                                                      | Mais informações                                                                                                                                                                         |
-|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <pre>auto-merge deployment api</pre>  | Merge automático do branch base através de uma implantação criada com a API                                                                                               | "[Criar uma implantação](/rest/reference/deployments#create-a-deployment)" na documentação da API REST                                                                                   |
-| <pre>blob#save</pre> | Mudar para o conteúdo de um arquivo na interface web                                                                                                                      | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                                     |
-| <pre>branch merge api</pre> | Merge de um branch através da API                                                                                                                                         | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST                                                                                               |
-| <pre>branches page delete button</pre> | Exclusão de um branch na interface web                                                                                                                                    | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)"      |
-| <pre>git refs create api</pre> | Criação de um ref através da API                                                                                                                                          | "[Banco de dados Git](/rest/reference/git#create-a-reference)" na documentação da API REST                                                                                               |
-| <pre>git refs delete api</pre> | Exclusão de uma ref através da API                                                                                                                                        | "[Banco de dados Git](/rest/reference/git#delete-a-reference)" na documentação da API REST                                                                                               |
-| <pre>git refs update api</pre> | Atualização de um ref através da API                                                                                                                                      | "[Banco de dados Git](/rest/reference/git#update-a-reference)" na documentação da API REST                                                                                               |
-| <pre>git repo contents api</pre> | Mudança no conteúdo de um arquivo através da API                                                                                                                          | "[Criar ou atualizar o conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)" na documentação da API REST                                                           |
-| <pre>merge base into head</pre> | Atualizar o branch de tópico do branch de base quando o branch de base exigir verificações de status rigorosas (via **Atualizar branch** em um pull request, por exemplo) | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)"                                                          |
-| <pre>pull request branch delete button</pre> | Exclusão de um branch de tópico de um pull request na interface web                                                                                                       | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
-| <pre>pull request branch undo button</pre> | Restauração de um branch de tópico de um pull request na interface web                                                                                                    | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)"                |
-| <pre>pull request merge api</pre> | Merge de um pull request através da API                                                                                                                                   | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" na documentação da API REST                                                                                                        |
-| <pre>pull request merge button</pre> | Merge de um pull request na interface web                                                                                                                                 | "[Fazer merge de uma pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)"                                         |
-| <pre>pull request revert button</pre> | Reverter um pull request                                                                                                                                                  | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)"                                                                              |
-| <pre>releases delete button</pre> | Exclusão de uma versão                                                                                                                                                    | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)"                                                         |
-| <pre>stafftools branch restore</pre> | Restauração de um branch do painel de administração do site                                                                                                               | "[Painel de administração do site](/admin/configuration/site-admin-dashboard#repositories)"                                                                                              |
-| <pre>tag create api</pre> | Criação de uma tag através da API                                                                                                                                         | "[Banco de dados Git](/rest/reference/git#create-a-tag-object)" na documentação da API REST                                                                                              |
-| <pre>slumlord (#<em>SHA</em>)</pre> | Commit por meio do Subversion                                                                                                                                             | "[Compatibilidade para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)"                                   |
-| <pre>web branch create</pre> | Criação de um branch através da interface web                                                                                                                             | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)"      |
+| Valor                      | Ação                                                                        | Mais informações                                                                                                                                                                    |
+|:-------------------------- |:--------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <pre>auto-merge deployment api</pre>  | Merge automático do branch base através de uma implantação criada com a API | "[Criar uma implantação](/rest/reference/deployments#create-a-deployment)" na documentação da API REST                                                                              |
+| <pre>blob#save</pre> | Mudar para o conteúdo de um arquivo na interface web                        | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                                |
+| <pre>branch merge api</pre> | Merge de um branch através da API                                           | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST                                                                                          |
+| <pre>branches page delete button</pre> | Exclusão de um branch na interface web                                      | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" |
+| <pre>git refs create api</pre> | Criação de um ref através da API                                            | "[Banco de dados Git](/rest/reference/git#create-a-reference)" na documentação da API REST                                                                                          |
+| <pre>git refs delete api</pre> | Exclusão de uma ref através da API                                          | "[Banco de dados Git](/rest/reference/git#delete-a-reference)" na documentação da API REST                                                                                          |
+| <pre>git refs update api</pre> | Atualização de um ref através da API                                        | "[Banco de dados Git](/rest/reference/git#update-a-reference)" na documentação da API REST                                                                                          |
+| <pre>git repo contents api</pre> | Mudança no conteúdo de um arquivo através da API                            | "[Criar ou atualizar o conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)" na documentação da API REST                                                      |
+
+{%- ifversion ghes > 3.0 %}
+| 
+
+`merge` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
+| <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | | <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | | <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | | <pre>pull request merge api</pre> | Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | | <pre>pull request merge button</pre> | Merge of a pull request in the web interface | "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | | <pre>pull request revert button</pre> | Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | | <pre>releases delete button</pre> | Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | | <pre>stafftools branch restore</pre> | Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | | <pre>tag create api</pre> | Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | | <pre>slumlord (#<em>SHA</em>)</pre> | Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | | <pre>web branch create</pre> | Creation of a branch via the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" |
 
 #### Disponível para merge de pull request
 
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index 7e6e8814e7..ed9461748e 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -9,6 +9,7 @@ redirect_from:
 intro: 'Após a criação de uma equipe, os administradores da organização podem adicionar usuários da {% data variables.product.product_location %} e determinar quais repositórios eles poderão acessar.'
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -30,8 +31,12 @@ Cada equipe tem suas próprias [ permissões de acesso definidas individualmente
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
+{% ifversion ghes %}
+
 ## Mapear equipes para grupos LDAP (em instâncias com sincronização LDAP para autenticação de usuários)
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
 Para adicionar um novo integrante a uma equipe sincronizada com um grupo LDAP, adicione o usuário como integrante do grupo LDAP ou entre em contato com o administrador do LDAP.
+
+{% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
index 8f8fc2cb7e..d71f847291 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
@@ -7,6 +7,7 @@ redirect_from:
   - /admin/user-management/continuous-integration-using-jenkins
 versions:
   ghes: '*'
+  ghae: '*'
 type: reference
 topics:
   - CI
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
index 52334965f2..e638566bb1 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/creating-teams
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -32,6 +33,8 @@ A prudent combination of teams is a powerful way to control repository access. F
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
 
+{% ifversion ghes %}
+
 ## Creating teams with LDAP Sync enabled
 
 Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
@@ -60,3 +63,5 @@ You must be a site admin and an organization owner to create a team with LDAP sy
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index a8a75333de..b59c6e86d3 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
 title: Gerenciar projetos usando o Jira
-intro: 'Você pode integrar o Jira com {% data variables.product.prodname_enterprise %} para o gerenciamento de projeto.'
+intro: 'Você pode integrar o Jira com {% data variables.product.product_name %} para o gerenciamento de projeto.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira
   - /enterprise/admin/articles/project-management-using-jira
@@ -10,6 +10,7 @@ redirect_from:
   - /admin/user-management/managing-projects-using-jira
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
index 48a3a781c8..cfcae7e41a 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/removing-users-from-teams-and-organizations
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -25,6 +26,8 @@ Somente proprietários ou administradores de equipe podem remover integrantes da
 
 ## Remover um integrante da equipe
 
+{% ifversion ghes %}
+
 {% warning %}
 
 **Observação:** {% data reusables.enterprise_management_console.badge_indicator %}
@@ -33,6 +36,8 @@ Para remover um integrante de uma equipe sincronizada com um grupo LDAP, entre e
 
 {% endwarning %}
 
+{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 80949adc4d..be8815c1c3 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -8,6 +8,7 @@ redirect_from:
   - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
   - /github/authenticating-to-github/creating-a-personal-access-token
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
+  - /github/extending-github/git-automation-with-oauth-tokens
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 5c3026036f..1da8ac4c25 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,11 @@ shortTitle: Chaves de implantação
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
 3. Na barra lateral esquerda, clique em **Deploy keys** (Chaves de implantação). ![Configuração das chaves de implantação](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
 4. Na página das chaves de implantação, anote as chaves de implantação associadas à sua conta. Para as chaves não reconhecidas ou desatualizadas, clique em **Delete** (Excluir). Se houver chaves de implantação válidas que deseja manter, clique em **Approve** (Aprovar). ![Lista de chaves de implantação](/assets/images/help/settings/settings-deploy-key-review.png)
 
 Para obter mais informações, consulte "[Gerenciar chaves de implantação](/guides/managing-deploy-keys)".
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
new file mode 100644
index 0000000000..2e6daf26d3
--- /dev/null
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
@@ -0,0 +1,119 @@
+---
+title: About code scanning alerts
+intro: 'Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About alerts from {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+## About alert details
+
+Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
+
+If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+
+When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+
+### About severity levels
+
+Alert severity levels may be `Error`, `Warning`, or `Note`.
+
+If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+### About security severity levels
+
+{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
+
+To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
+
+By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+### About labels for alerts that are not found in application code
+
+{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
+
+- **Generated**: Code generated by the build process
+- **Test**: Test code
+- **Library**: Library or third-party code
+- **Documentation**: Documentation
+
+{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
+
+Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
+
+![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
+
+On the alert page, you can see that the filepath is marked as library code (`Library` label).
+
+![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
+
+{% if codeql-ml-queries %}
+
+## About experimental alerts
+
+{% data reusables.code-scanning.beta-codeql-ml-queries %}
+
+In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
+
+![Code scanning experimental alert in list](/assets/images/help/repository/code-scanning-experimental-alert-list.png)
+
+### Benefits of using machine learning models to extend queries
+
+Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
+
+Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
+
+{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
+
+### Alerts identified using machine learning
+
+Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
+
+![Code scanning experimental alert details](/assets/images/help/repository/code-scanning-experimental-alert-show.png)
+
+## Enabling experimental alerts
+
+The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you update your workflow to run an additional query suite this will increase the analysis time.
+
+``` yaml
+- uses: github/codeql-action/init@v1
+  with:
+    # Run extended queries including queries using machine learning
+    queries: security-extended
+```
+
+For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+## Disabling experimental alerts
+
+The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
+
+- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
+- Specify details of the repositories or organizations that are affected
+- Request an escalation to engineering
+
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index 3db8e3f7f2..a2eae3015f 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -43,7 +43,7 @@ O {% data variables.product.prodname_codeql %} é compatível com linguagens com
 
 ## Sobre consultas de {% data variables.product.prodname_codeql %}
 
-{% data variables.product.company_short %} especialistas, pesquisadores de segurança e contribuidores da comunidade escrevem e mantêm as consultas padrão de {% data variables.product.prodname_codeql %} usadas por {% data variables.product.prodname_code_scanning %}. As consultas são regularmente atualizadas para melhorar a análise e reduzir quaisquer resultados falso-positivos. As consultas são de código aberto.Portanto, você pode ver e contribuir para as consultas no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) no site do GitHub Security Lab. Você também pode escrever suas próprias consultas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" na documentação do {% data variables.product.prodname_codeql %}.
+{% data variables.product.company_short %} especialistas, pesquisadores de segurança e contribuidores da comunidade escrevem e mantêm as consultas padrão de {% data variables.product.prodname_codeql %} usadas por {% data variables.product.prodname_code_scanning %}. As consultas são regularmente atualizadas para melhorar a análise e reduzir quaisquer resultados falso-positivos. As consultas são de código aberto.Portanto, você pode ver e contribuir para as consultas no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://codeql.github.com/) no site {% data variables.product.prodname_codeql %} Você também pode escrever suas próprias consultas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" na documentação do {% data variables.product.prodname_codeql %}.
 
 Você pode executar consultas adicionais como parte da sua análise de digitalização de código.
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index 4b6f4aa540..d49a26c6e9 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -18,7 +18,6 @@ topics:
   - Code scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index eafbc64c0b..af256d5d03 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -24,7 +24,7 @@ topics:
   - Python
 shortTitle: Configure code scanning
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
@@ -89,7 +89,7 @@ If you scan pull requests, then the results appear as alerts in a pull request c
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ### Defining the severities causing pull request check failure
 
-By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)."
+By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -351,7 +351,7 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 
 You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 {% if codeql-packs %}
 ### Working with custom configuration files
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 99310dae0e..0094d9ab1e 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -27,7 +27,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 622a6eb37f..6c1d00f0ab 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -16,6 +16,7 @@ topics:
   - Code scanning
 children:
   - /about-code-scanning
+  - /about-code-scanning-alerts
   - /triaging-code-scanning-alerts-in-pull-requests
   - /setting-up-code-scanning-for-a-repository
   - /managing-code-scanning-alerts-for-your-repository
@@ -28,4 +29,4 @@ children:
   - /running-codeql-code-scanning-in-a-container
   - /viewing-code-scanning-logs
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index bc07386975..c5bbaac064 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
-title: Managing code scanning alerts for your repository
-shortTitle: Manage alerts
-intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
+title: Gerenciar alertas de verificação de código para o seu repositório
+shortTitle: Gerenciar alertas
+intro: 'Da visão de segurança, você pode visualizar, corrigir, ignorar ou excluir alertas de potenciais vulnerabilidades ou erros no código do seu projeto.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -23,162 +23,105 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
-## About alerts from {% data variables.product.prodname_code_scanning %}
+## Visualizar os alertas de um repositório
 
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+Qualquer pessoa com permissão de leitura para um repositório pode ver anotações de {% data variables.product.prodname_code_scanning %} em pull requests. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
 
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+Você precisa de permissão de gravação para visualizar um resumo de todos os alertas para um repositório na aba **Segurança**.
 
-{% data reusables.code-scanning.upload-sarif-alert-limit %}
-
-## About alerts details
-
-Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
-
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
-
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
-
-When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
-
-### About severity levels
-
-Alert severity levels may be `Error`, `Warning`, or `Note`.
-
-By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### About security severity levels
-
-{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
-
-To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
-
-By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-### About labels for alerts that are not found in application code
-
-{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
-
-- **Generated**: Code generated by the build process
-- **Test**: Test code
-- **Library**: Library or third-party code
-- **Documentation**: Documentation
-
-{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
-
-Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code.
-
-![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
-
-On the alert page, you can see that the filepath is marked as library code (`Library` label).
-
-![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
-
-## Viewing the alerts for a repository
-
-Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-
-You need write permission to view a summary of all the alerts for a repository on the **Security** tab.
-
-By default, the code scanning alerts page is filtered to show alerts for the default branch of the repository only.
+Por padrão, a página de verificação de código de alertas é filtrada para mostrar alertas apenas para o branch padrão do repositório.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts.
-   ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %}
+1. Opcionalmente, use a caixa de pesquisa de texto livre ou os menus suspensos para filtrar alertas. Por exemplo, você pode filtrar pela ferramenta usada para identificar alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %}
 {% data reusables.code-scanning.explore-alert %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-   ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png)
+   ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png)
 {% else %}
-   ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
+   ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
 {% endif %}
-1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used.
-   ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png)
-1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
-   ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
+1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png)
+1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png)
+
+For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
 
-**Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. 
+**Observação:** Para análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}, você pode ver informações sobre a última execução em um cabeçalho na parte superior da lista de alertas de {% data variables.product.prodname_code_scanning %} para o repositório.
 
-For example, you can see when the last scan ran, the number of lines of code analyzed compared to the total number of lines of code in your repository, and the total number of alerts that were generated.
-  ![UI banner](/assets/images/help/repository/code-scanning-ui-banner.png)
+Por exemplo, você pode ver quando o último scanner foi executada, o número de linhas de código analisadas em comparação com o número total de linhas de código no seu repositório, e o número total de alertas gerados. ![Banner de interface do usuário](/assets/images/help/repository/code-scanning-ui-banner.png)
 
 {% endnote %}
 {% endif %}
 
-## Filtering {% data variables.product.prodname_code_scanning %} alerts
+## Filtrando alertas de {% data variables.product.prodname_code_scanning %}
 
-You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. 
+Você pode filtrar os alertas exibidos no modo de exibição de alertas de {% data variables.product.prodname_code_scanning %}. Isso é útil caso haja muitos alertas pois você pode se concentrar em um determinado tipo de alerta. Existem alguns filtros predefinidos e uma série de palavras-chave que você pode usar para refinar a lista de alertas exibidos.
 
-- To use a predefined filter, click **Filters**, or a filter shown in the header of the list of alerts, and choose a filter from the drop-down list.
-  {% ifversion fpt or ghes > 3.0 or ghec %}![Predefined filters](/assets/images/help/repository/code-scanning-predefined-filters.png)
+- Para usar um filtro predefinido, clique **Filtros** ou em um filtro exibido no cabeçalho da lista de alertas e escolha um filtro na lista suspensa.
+  {% ifversion fpt or ghes > 3.0 or ghec %}![Filtros predefinidos](/assets/images/help/repository/code-scanning-predefined-filters.png)
   {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %}
-- To use a keyword, either type directly in the filters text box, or:
-  1. Click in the filters text box to show a list of all available filter keywords.
-  2. Click the keyword you want to use and then choose a value from the drop-down list.
-  ![Keyword filters list](/assets/images/help/repository/code-scanning-filter-keywords.png)
+- Para usar uma palavra-chave, digite diretamente na caixa de texto dos filtros ou:
+  1. Clique na caixa de filtros para exibir uma lista de todas as palavras-chave de filtro disponíveis.
+  2. Clique na palavra-chave que deseja usar e, em seguida, selecione um valor na lista suspensa. ![Lista de filtros de palavra-chave](/assets/images/help/repository/code-scanning-filter-keywords.png)
 
-The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results.
+O benefício de usar filtros de palavra-chave é que apenas os valores com resultados são exibidos nas listas suspensas. Isso facilita evitar filtros de configuração que não encontram resultados.
 
-If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch.
+Se você inserir vários filtros, a visualização mostrará alertas que correspondem a _todos_ esses filtros. Por exemplo, `is:closed severity:high branch:main` só exibirá alertas de alta gravidade fechados e que estão presentes no branch `principal`. A exceção são os filtros relacionados a refs (`ref`, `branch` e `pr`): `is:open branch:main branch:next` irá mostrar alertas abertos do branch `principal` do `próximo` branch.
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 
-You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
+Você pode prefixar o filtro `tag` com `-` para excluir resultados com essa tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
 
 {% endif %}
 
-### Restricting results to application code only
+### Restringir resultados apenas ao código do aplicativo
 
-You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code.
+Você pode usar o filtro "Apenas alertas no código do aplicativo" ou a palavra-chave `autofilter:true` e valor para restringir os resultados de alertas no código do aplicativo. Consulte "[Sobre etiquetas para alertas que não estão no código de aplicativos](#about-labels-for-alerts-that-are-not-found-in-application-code)" acima para mais informações sobre os tipos de código que não são código do aplicativo.
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
 
-## Searching {% data variables.product.prodname_code_scanning %} alerts
+## Pesquisando alertas de {% data variables.product.prodname_code_scanning %}
 
-You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across:
-- The name of the alert
-- The alert description
-- The alert details (this also includes the information hidden from view by default in the **Show more** collapsible section)
+Você pode pesquisar na lista de alertas. Isso é útil se houver um grande número de alertas no seu repositório, ou, por exemplo, se você não souber o nome exato de um alerta. {% data variables.product.product_name %} realiza a pesquisa de texto livre:
+- O nome do alerta
+- A descrição do alerta
+- Os detalhes do alerta (isso também inclui as informações ocultas da visualização por padrão na seção ocultável **Mostrar mais**)
 
- ![The alert information used in searches](/assets/images/help/repository/code-scanning-free-text-search-areas.png)
+ ![Informações de alerta usadas em pesquisas](/assets/images/help/repository/code-scanning-free-text-search-areas.png)
 
-| Supported search | Syntax example | Results |
-| ---- | ---- | ---- |
-| Single word search | `injection` | Returns all the alerts containing the word `injection` |
-| Multiple word search | `sql injection` | Returns all the alerts containing `sql` or `injection` |
-| Exact match search</br>(use double quotes) |  `"sql injection"` | Returns all the alerts containing the exact phrase `sql injection` |
-| OR search | `sql OR injection` | Returns all the alerts containing `sql` or `injection` |
-| AND search | `sql AND injection` | Returns all the alerts containing both words `sql` and `injection` | 
+| Pesquisa compatível                                      | Exemplo de sintaxe | Resultados                                                              |
+| -------------------------------------------------------- | ------------------ | ----------------------------------------------------------------------- |
+| Pesquisa de uma palavra                                  | `injeção`          | Retorna todos os alertas que contêm a palavra `injeção`                 |
+| Pesquisa de múltiplas palavras                           | `injeção sql`      | Retorna todos os alertas que contêm `sql` ou `injeção`                  |
+| Pesquisa de correspondência exata</br>(use aspas duplas) | `"injeção sql"`    | Retorna todos os alertas que contém a frase exata `injection sql`       |
+| OU pesquisa                                              | `sql OU injeção`   | Retorna todos os alertas que contêm `sql` ou `injeção`                  |
+| Pesquisa E                                               | `sql E injeção`    | Retorna todos os alertas que contêm ambas as palavras `sql` e `injeção` |
 
 {% tip %}
 
-**Tips:** 
-- The multiple word search is equivalent to an OR search.
-- The AND search will return results where the search terms are found _anywhere_, in any order in the alert name, description, or details.
+**Dicas:**
+- A busca múltipla de palavras é equivalente a uma busca OU.
+- A busca E retornará resultados em que os termos da pesquisa são encontrados _em qualquer lugar_, em qualquer ordem no nome do alerta, descrição ou detalhes.
 
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-1. To the right of the **Filters** drop-down menus, type the keywords to search for in the free text search box.
-  ![The free text search box](/assets/images/help/repository/code-scanning-search-alerts.png)
-2. Press <kbd>return</kbd>. The alert listing will contain the open {% data variables.product.prodname_code_scanning %} alerts matching your search criteria.
+1. À direita dos menus suspensos de **Filtros**, digite as palavras-chave a serem pesquisadas na caixa de pesquisa de texto livre. ![A caixa de pesquisa de texto livre](/assets/images/help/repository/code-scanning-search-alerts.png)
+2. Pressione <kbd>retornar</kbd>. O anúncio do alerta conterá os alertas {% data variables.product.prodname_code_scanning %} alertas abertos correspondentes aos seus critérios de busca.
 
 {% endif %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
-## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
+{% if code-scanning-task-lists %}
+## Rastreando alertas de {% data variables.product.prodname_code_scanning %} em problemas
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
 {% data reusables.code-scanning.github-issues-integration %}
@@ -186,80 +129,79 @@ You can search the list of alerts. This is useful if there is a large number of
 
 {% endif %}
 
-## Fixing an alert
+## Corrigir um alerta
 
-Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+Qualquer pessoa com permissão de gravação para um repositório pode corrigir um alerta, fazendo o commit de uma correção do código. Se o repositório tiver {% data variables.product.prodname_code_scanning %} agendado para ser executado em pull requests, recomenda-se registrar um pull request com sua correção. Isso ativará a análise de {% data variables.product.prodname_code_scanning %} referente às alterações e irá testar se sua correção não apresenta nenhum problema novo. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e " "[Testar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
+Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra alertas e alertas corrigidos que os usuários ignoraram.
 
-You can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. 
+Você pode usar{% ifversion fpt or ghes > 3.1 or ghae or ghec %} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, marcar, por sua vez, todos os alertas correspondentes como fechados.
 
-Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
+Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png)
+![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png)
 {% else %}
-![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
+![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-## Dismissing or deleting alerts
+## Ignorar ou excluir alertas
 
-There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
+Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**.
 
-Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
+Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**.
 
-When you dismiss an alert:
+Ao descartar um alerta:
 
-- It's dismissed in all branches.
-- The alert is removed from the number of current alerts for your project.
-- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
-- The reason why you closed the alert is recorded.
-- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
+- Ele é ignorado em todos os branches.
+- O alerta é removido do número de alertas atuais para o seu projeto.
+- O alerta é movido para a lista "Fechado" no resumo dos alertas, onde você pode reabri-lo, se necessário.
+- O motivo pelo qual você fechou o alerta foi gravado.
+- Da próxima vez que {% data variables.product.prodname_code_scanning %} for executado, o mesmo código não gerará um alerta.
 
-When you delete an alert:
+Ao excluir um alerta:
 
-- It's deleted in all branches.
-- The alert is removed from the number of current alerts for your project.
-- It is _not_ added to the "Closed" list in the summary of alerts.
-- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.
+- Ele é excluído em todos os branches.
+- O alerta é removido do número de alertas atuais para o seu projeto.
+- Ele _não é_ adicionado à lista "Fechado" no resumo dos alertas.
+- Se o código que gerou o alerta permanecer o mesmo, e a mesma ferramenta {% data variables.product.prodname_code_scanning %} for executada novamente sem qualquer alteração de configuração, o alerta será exibido novamente nos resultados das análises.
 
-To dismiss or delete alerts:
+Para ignorar ou excluir alertas:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
+1. Se você tem permissões de administrador para o repositório e deseja excluir alertas para esta ferramenta de {% data variables.product.prodname_code_scanning %}, selecione algumas ou todas as caixas de seleção e clique em **Excluir**.
 
-   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
+   ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png)
 
-   Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae or ghec %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
+   Opcionalmente, você pode usar{% ifversion fpt or ghes > 3.1 or ghae or ghec %}} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas correspondentes de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-  ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png)
+  ![Filtrar alertas por regra](/assets/images/help/repository/code-scanning-filter-by-rule.png)
 {% else %}
-  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
+  ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
 {% endif %}
 
-1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
+1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-   ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png)
+   ![Abrir um alerta da lista de resumo](/assets/images/help/repository/code-scanning-click-alert.png)
 {% else %}
-  ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
+  ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
 {% endif %}
-1. Review the alert, then click **Dismiss** and choose a reason for closing the alert.
-   ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
    {% data reusables.code-scanning.choose-alert-dismissal-reason %}
 
    {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-### Dismissing multiple alerts at once
+### Ignorar múltiplos alertas de uma vez
 
-If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
+Se um projeto tem vários alertas que você deseja ignorar pelo mesmo motivo, você pode ignorá-los em massa do resumo de alertas. Normalmente, você pode querer filtrar a lista e, em seguida, ignorar todos os alertas correspondentes. Por exemplo, você pode querer ignorar todos os alertas atuais no projeto que foram marcados para uma vulnerabilidade específica de Enumeração de Fraqueza Comum (CWE).
 
-## Further reading
+## Leia mais
 
-- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
-- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"
-- "[About integration with {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)"
+- "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
+- "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"
+- "[Sobre a integração com {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)"
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index 42167176df..b779547b88 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -23,7 +23,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index 4cc299ead5..de19795d71 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -5,9 +5,7 @@ intro: Você pode adicionar alertas de digitalização de código a problemas us
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
-  fpt: '*'
-  ghes: '> 3.3'
-  ghae: issue-5036
+  feature: code-scanning-task-lists
 type: how_to
 topics:
   - Advanced Security
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index c35f771051..a7458d34b7 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -22,7 +22,6 @@ topics:
   - Repositories
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index f4bfbebb63..4271ef318a 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -27,7 +27,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
@@ -189,6 +188,19 @@ Se você dividir sua análise em vários fluxos de trabalho, conforme descrito a
 
 <p spaces-before="0">Se sua análise ainda é muito lenta para ser executada durante eventos <code>push` ou `pull_request`, você poderá acionar apenas a análise no evento `agendamento`. Para obter mais informações, consulte "[Eventos](/actions/learn-github-actions/introduction-to-github-actions#events)".</p>
 
+### Check which query suites the workflow runs
+
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
+
+You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+{% if codeql-ml-queries %}
+{% note %}
+
+**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+{% endnote %}
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ## Os resultados diferem entre as plataformas de análise
 
@@ -204,7 +216,7 @@ Se a execução de um fluxo de trabalho para {% data variables.product.prodname_
 
 ## Erro: "Fora do disco" ou "Sem memória"
 
-Em projetos muito grandes, {% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor.
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
 {% ifversion fpt or ghec %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema.
 {% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %}
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/index.md b/translations/pt-BR/content/code-security/code-scanning/index.md
index ef7bc75ce6..ceaad8145b 100644
--- a/translations/pt-BR/content/code-security/code-scanning/index.md
+++ b/translations/pt-BR/content/code-security/code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /using-codeql-code-scanning-with-your-existing-ci-system
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
index 9bbe4dbac6..96f580d43d 100644
--- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -20,7 +20,6 @@ topics:
   - Integration
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/index.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/index.md
index 71870086eb..7992326af1 100644
--- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/index.md
+++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /sarif-support-for-code-scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index ab3879863f..c1fc8e6166 100644
--- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -21,7 +21,7 @@ topics:
   - Integration
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index c0b9b3afea..0beaf40ec0 100644
--- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -24,7 +24,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index 7c42e31833..6105ca77b6 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -28,7 +28,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
@@ -83,7 +83,7 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index 28abc670f2..689ba5e383 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -28,4 +28,3 @@ children:
   - /migrating-from-the-codeql-runner-to-codeql-cli
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index b9bf8d50fe..86e15795a1 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -26,7 +26,6 @@ topics:
   - SARIF
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
index e475f46906..2be61d2b66 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -24,7 +24,6 @@ topics:
   - CI
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
index ea28237764..25e29b59c1 100644
--- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
@@ -139,3 +139,9 @@ Você pode visualizar e gerenciar alertas de funcionalidades de segurança para
 
 {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)".
 {% endif %}
+
+{% ifversion ghec %}
+## Leia mais
+
+"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/guides.md b/translations/pt-BR/content/code-security/guides.md
index 2cc290e407..2f036cb2de 100644
--- a/translations/pt-BR/content/code-security/guides.md
+++ b/translations/pt-BR/content/code-security/guides.md
@@ -30,6 +30,7 @@ includeGuides:
   - /code-security/secret-scanning/secret-scanning-partners
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index 74689680bf..026aa0ca3d 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,6 +27,6 @@ Você também pode bloquear usuários. Para obter mais informações, consulte "
 ## Limitar interações para sua conta de usuário
 
 {% data reusables.user_settings.access_settings %}
-1. Na barra lateral de configurações do usuário, em "Configurações de moderação", clique em **Limites de interação**. ![Aba "Limites de interação" na barra lateral de configurações do usuário](/assets/images/help/settings/settings-sidebar-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index 02a4dc36ad..cbfb92cdf4 100644
--- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -40,7 +40,7 @@ Você pode definir as seguintes chaves de nível superior para cada formulário
 | `descrição` | Uma descrição para o modelo de formulário de problema, que aparece na interface de modelo de seletor.                          | Obrigatório | string                                    |
 | `texto`     | Definição dos tipos de entrada no formulário.                                                                                  | Obrigatório | Array                                     |
 | `assignees` | As pessoas que serão automaticamente atribuídas a problemas criados com este modelo.                                           | Opcional    | Matriz ou strings delimitadas por vírgula |
-| `etiquetas` | Etiquetas que serão adicionadas automaticamente a problemas criados com este modelo.                                           | Opcional    | string                                    |
+| `etiquetas` | Etiquetas que serão adicionadas automaticamente a problemas criados com este modelo.                                           | Opcional    | Matriz ou strings delimitadas por vírgula |
 | `title`     | Um título padrão que será preenchido no formulário de envio do problema.                                                       | Opcional    | string                                    |
 
 Para os tipos de entrada disponíveis `texto` e suas sintaxes, consulte "[Sintaxe para o esquema de formulário {% data variables.product.prodname_dotcom %}](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)".
diff --git a/translations/pt-BR/content/developers/overview/about-githubs-apis.md b/translations/pt-BR/content/developers/overview/about-githubs-apis.md
index 86ae7850ad..0ec175872b 100644
--- a/translations/pt-BR/content/developers/overview/about-githubs-apis.md
+++ b/translations/pt-BR/content/developers/overview/about-githubs-apis.md
@@ -3,6 +3,8 @@ title: Sobre as APIs do GitHub
 intro: 'Saiba mais sobre as APIs dos {% data variables.product.prodname_dotcom %} para estender e personalizar sua experiência no {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /v3/versions
+  - /articles/getting-started-with-the-api
+  - /github/extending-github/getting-started-with-the-api
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
index a06eff2199..3fa0b6fdd6 100644
--- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
+++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
@@ -34,11 +34,11 @@ Em muitos casos, especialmente no início de um projeto, o encaminhamento de age
 #### Configuração
 
 1. Ativar o encaminhamento do agente localmente. Consulte o [nosso guia sobre o encaminhamento de agentes SSH][ssh-agent-forwarding] para obter mais informações.
-2. Defina seus scripts de implantação para usar o encaminhamento de agentes. Por exemplo, em um script bash, permitir o encaminhamento de agentes seria algo como isto: `ssh -A serverA 'bash -s' < deploy.sh`
+2. Defina seus scripts de implantação para usar o encaminhamento de agentes. For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh`
 
 ## Clonagem de HTTPS com tokens do OAuth
 
-Se você não quiser usar chaves SSH, você poderá usar [HTTPS com tokens do OAuth][git-automation].
+If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
 
 #### Prós
 
@@ -57,7 +57,7 @@ Se você não quiser usar chaves SSH, você poderá usar [HTTPS com tokens do OA
 
 #### Configuração
 
-Consulte o [nosso guia sobre automação Git com tokens][git-automation].
+See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
 ## Chaves de implantação
 
@@ -184,9 +184,6 @@ Isto significa que você não pode automatizar a criação de contas. Mas se voc
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
-[git-automation]: /articles/git-automation-with-oauth-tokens
-[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
-
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
new file mode 100644
index 0000000000..a71393cc16
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
@@ -0,0 +1,36 @@
+---
+title: Sobre o GitHub Marketplace
+intro: 'O {% data variables.product.prodname_marketplace %} contém ferramentas que adicionam funcionalidade e aprimoram seu fluxo de trabalho.'
+redirect_from:
+  - /articles/about-github-marketplace
+  - /github/customizing-your-github-workflow/about-github-marketplace
+  - /github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+Você pode descobrir, navegar e instalar ferramentas grátis e pagas, incluindo {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_actions %}, em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
+
+Ao comprar uma ferramenta paga, você pagará pela assinatura da sua ferramenta com as mesmas informações de cobrança usadas para pagar sua assinatura do {% data variables.product.product_name %} e receberá uma fatura na data regular da cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
+
+Em algumas ferramentas, você tem a opção de selecionar uma avaliação gratuita de 14 dias. É possível fazer o cancelamento a qualquer momento durante a avaliação, e você não será cobrado, mas perderá automaticamente o acesso à ferramenta. A assinatura paga começará a ser contada no fim da versão de avaliação de 14 dias. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
+
+## Encontrar ferramentas em {% data variables.product.prodname_marketplace %}
+
+Você pode descobrir, navegar e instalar aplicativos e ações criados por outros em {% data variables.product.prodname_marketplace %}. Consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)".
+
+{% data reusables.actions.actions-not-verified %}
+
+Qualquer um pode listar um {% data variables.product.prodname_github_app %} ou {% data variables.product.prodname_oauth_app %} grátis em {% data variables.product.prodname_marketplace %}. Os publicadores de aplicativos pagos são verificados por {% data variables.product.company_short %} e os anúncios desses aplicativos são mostrados com um selo do marketplace de {% octicon "verified" aria-label="Verified creator badge" %}. Você também verá selos para aplicativos não verificados e verificados. Esses apps foram publicados usando o método anterior para verificar aplicativos individuais. Para obter mais informações sobre o processo atual, consulte "[Sobre o GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" e "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)."
+
+## Criar e listar uma ferramenta no {% data variables.product.prodname_marketplace %}
+
+Para obter mais informações sobre a criação de sua própria ferramenta para listar em {% data variables.product.prodname_marketplace %}, consulte "[Aplicativos](/developers/apps)" e "[{% data variables.product.prodname_actions %}](/actions)".
+
+## Leia mais
+
+- "[Comprar e instalar apps no {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)"
+- "[Gerenciar cobrança para aplicativos do {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)"
+- "[Suporte do {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)"
+- "[Diferenças entre aplicativos aplicativos GitHub e OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)"
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
new file mode 100644
index 0000000000..8894ea071a
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -0,0 +1,43 @@
+---
+title: Sobre integrações
+intro: 'As integrações são ferramentas e serviços que se conectam ao {% data variables.product.product_name %} para complementar e estender o fluxo de trabalho.'
+redirect_from:
+  - /articles/about-integrations
+  - /github/customizing-your-github-workflow/about-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/about-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+Você pode instalar integrações em sua conta pessoal ou em organizações que possui. Você também pode instalar {% data variables.product.prodname_github_apps %} a partir de um repositório específico em um repositório específico em que você tem permissões de administrador ou que pertencem à sua organização.
+
+## Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}
+
+As integrações podem ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, ou qualquer coisa que utilize {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs ou webhooks.
+
+{% data variables.product.prodname_github_apps %} oferecem permissões granulares e solicitam acesso apenas ao que o aplicativo precisa. {% data variables.product.prodname_github_apps %} também oferece permissões específicas no nível de usuário que cada um deve autorizar individualmente quando um aplicativo está instalado ou quando o integrador altera as permissões solicitadas pelo aplicativo.
+
+Para obter mais informações, consulte:
+- "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
+- "[Sobre aplicativos](/apps/about-apps/)"
+- "[Permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
+- "[Autorizar {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Autorizar {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[Revisar integrações autorizadas](/articles/reviewing-your-authorized-integrations/)"
+
+Será possível instalar um {% data variables.product.prodname_github_app %} pré-configurado se os integradores ou criadores de app tiverem criado o respectivo app com o fluxo de manifesto do {% data variables.product.prodname_github_app %}. Para obter informações sobre como executar o {% data variables.product.prodname_github_app %} com configuração automatizada, entre em contato com o integrador ou criador do app.
+
+Você poderá criar um {% data variables.product.prodname_github_app %} com configuração simplificada se usar o Probot. Para obter mais informações, consulte o site de [documentos do Probot](https://probot.github.io/docs/).
+
+## Descobrir integrações no {% data variables.product.prodname_marketplace %}
+
+É possível encontrar uma integração para instalar ou publicar a sua própria integração no {% data variables.product.prodname_marketplace %}.
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contém {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}. Para obter mais informações sobre como encontrar uma integração ou criar sua própria integração, consulte "[Sobre o {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)".
+
+## Integrações compradas diretamente de integradores
+
+Você também pode comprar algumas integrações diretamente de integradores. Como um integrante da organização, ao encontrar um {% data variables.product.prodname_github_app %} que queira usar, você poderá solicitar que uma organização aprove e instale o app para a organização.
+
+Se você tiver permissões de administrador para todos os repositórios de organizações em que o app está instalado, você poderá instalar {% data variables.product.prodname_github_apps %} com permissões de nível de repositório sem ter que solicitar que o proprietário da organização aprove o aplicativo. Quando um integrador altera as permissões do app, se as permissões forem apenas para um repositório, os proprietários da organização e as pessoas com permissões de administrador para um repositório com esse app instalado poderão revisar e aceitar as novas permissões.
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
new file mode 100644
index 0000000000..3a6aee41cc
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
@@ -0,0 +1,32 @@
+---
+title: Sobre webhooks
+redirect_from:
+  - /post-receive-hooks
+  - /articles/post-receive-hooks
+  - /articles/creating-webhooks
+  - /articles/about-webhooks
+  - /github/extending-github/about-webhooks
+intro: Webhooks permitem que notificações sejam entregues a um servidor web externo sempre que determinadas ações ocorrem em um repositório ou uma organização.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% tip %}
+
+**Dica:** {% data reusables.organizations.owners-and-admins-can %} gerenciar webhooks para uma organização. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+Os webhooks podem ser acionados sempre que uma variedade de ações for executada em um repositório ou uma organização. Por exemplo, você pode configurar um webhook para ser executado sempre que:
+
+* É feito push de um repositório
+* Uma pull request é aberta
+* Um site do {% data variables.product.prodname_pages %} é construído
+* Um novo integrante é adicionado a uma equipe
+
+Ao usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, você pode fazer esses webhooks atualizarem um rastreador de problemas externo, acionar compilações de CI, atualizar um espelho de backup, ou até mesmo fazer a implantação no seu servidor de produção.
+
+Para configurar um novo webhook, você deverá acessar um servidor externo e ter familiaridade com os procedimentos técnicos envolvidos. Para obter ajuda sobre como criar um webhook, incluindo uma lista completa de ações que podem ser associadas a ele, consulte "[Webhooks](/webhooks)."
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
new file mode 100644
index 0000000000..086fc51c68
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -0,0 +1,54 @@
+---
+title: GitHub extensions and integrations
+intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
+redirect_from:
+  - /articles/about-github-extensions-for-third-party-applications
+  - /articles/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Extensions & integrations
+---
+## Editor tools
+
+You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio.
+
+### {% data variables.product.product_name %} for Atom
+
+With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/).
+
+### {% data variables.product.product_name %} for Unity
+
+With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
+
+### {% data variables.product.product_name %} for Visual Studio
+
+With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+
+### {% data variables.product.prodname_dotcom %} for Visual Studio Code
+
+With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+
+## Project management tools
+
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
+
+### Jira Cloud and {% data variables.product.product_name %}.com integration
+
+You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
+
+## Team communication tools
+
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
+
+### Slack and {% data variables.product.product_name %} integration
+
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. 
+
+The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.
+
+### Microsoft Teams and {% data variables.product.product_name %} integration
+
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
new file mode 100644
index 0000000000..ea12da5a6a
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
@@ -0,0 +1,18 @@
+---
+title: Explorar integrações
+intro: 'É possível personalizar e estender o fluxo de trabalho do {% data variables.product.product_name %} com ferramentas e serviços criados pela comunidade do {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/exploring-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-integrations
+  - /about-webhooks
+  - /about-github-marketplace
+  - /github-extensions-and-integrations
+---
+
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/index.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/index.md
new file mode 100644
index 0000000000..fd86ccadeb
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/index.md
@@ -0,0 +1,17 @@
+---
+title: Personalizar o fluxo de trabalho do GitHub
+intro: 'Learn how you can customize your {% data variables.product.prodname_dotcom %} workflow with extensions, integrations, {% data variables.product.prodname_marketplace %}, and webhooks.'
+redirect_from:
+  - /categories/customizing-your-github-workflow
+  - /github/customizing-your-github-workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: '*'
+  ghes: '*'
+children:
+  - /exploring-integrations
+  - /purchasing-and-installing-apps-in-github-marketplace
+shortTitle: Personalize seu fluxo de trabalho
+---
+
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
new file mode 100644
index 0000000000..9558e98091
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
@@ -0,0 +1,15 @@
+---
+title: Comprar e instalar apps no GitHub Marketplace
+intro: 'O {% data variables.product.prodname_marketplace %} inclui apps com planos de preços pagos e gratuitos. Quando encontrar um app pago que gostaria de usar em sua conta pessoal ou organização, você pode comprar e instalar o app usando suas informações de cobrança existentes.'
+redirect_from:
+  - /articles/purchasing-and-installing-apps-in-github-marketplace
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /installing-an-app-in-your-personal-account
+  - /installing-an-app-in-your-organization
+shortTitle: Instalar aplicativos do Marketplace
+---
+
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
new file mode 100644
index 0000000000..15f6c2b883
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: Instalar aplicativos na organização
+intro: 'É possível instalar aplicativos do {% data variables.product.prodname_marketplace %} para usar em sua organização.'
+redirect_from:
+  - /articles/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Instalar organização de aplicativos
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+Se você escolheu um plano pago, a assinatura do app será paga na data de cobrança atual de sua organização e com a forma de pagamento vigente.
+
+{% data reusables.marketplace.free-trials %}
+
+## Instalar um {% data variables.product.prodname_github_app %} em sua organização
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Se o app solicitar acesso a repositórios, decida se quer dar acesso a todos ou apenas determinados repositórios e selecione **All repositories** (Todos os repositórios) ou **Only select repositories** (Somente repositórios selecionados). ![Botões com opções para instalar um app em todos ou apenas determinados repositórios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## Instalar um {% data variables.product.prodname_oauth_app %} em sua organização
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Revise as informações sobre o acesso do app à sua conta pessoal, organização e dados, e depois clique em **Authorize application** (Autorizar aplicativo).
+
+## Leia mais
+
+- "[Atualizar a forma de pagamento da sua organização](/articles/updating-your-organization-s-payment-method)"
+- "[Instalar um app em sua conta pessoal](/articles/installing-an-app-in-your-personal-account)"
diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
new file mode 100644
index 0000000000..4765b8e4bc
--- /dev/null
+++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -0,0 +1,49 @@
+---
+title: Instalar aplicativos em sua conta pessoal
+intro: 'É possível instalar aplicativos de {% data variables.product.prodname_marketplace %} para usar em sua conta pessoal.'
+redirect_from:
+  - /articles/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Instalar uma conta de usuário do aplicativo
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+Se você escolheu um plano pago, a assinatura de seu app será paga na data de cobrança atual de sua conta pessoal e com a forma de pagamento vigente.
+
+{% data reusables.marketplace.free-trials %}
+
+## Instalar um {% data variables.product.prodname_github_app %} em sua conta pessoal
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Decida se quer dar acesso ao app a todos ou apenas determinados repositórios e selecione **All repositories** (Todos os repositórios) ou **Only select repositories** (Somente repositórios selecionados). ![Botões com opções para instalar um app em todos ou apenas determinados repositórios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## Instalar um {% data variables.product.prodname_oauth_app %} em sua conta pessoal
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. Revise as informações sobre o acesso do app à sua conta pessoal e dados, e depois clique em **Authorize application** (Autorizar aplicativo).
+
+## Leia mais
+
+- "[Atualizar a forma de pagamento da sua conta pessoal](/articles/updating-your-personal-account-s-payment-method)"
+- "[Instalar um app em sua organização](/articles/installing-an-app-in-your-organization)"
diff --git a/translations/pt-BR/content/get-started/index.md b/translations/pt-BR/content/get-started/index.md
index 49a9dd08cd..23f145e3d6 100644
--- a/translations/pt-BR/content/get-started/index.md
+++ b/translations/pt-BR/content/get-started/index.md
@@ -62,6 +62,7 @@ children:
   - /exploring-projects-on-github
   - /getting-started-with-git
   - /using-git
+  - /customizing-your-github-workflow
   - /privacy-on-github
 ---
 
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index cff9f554b3..591fb7be11 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -12,7 +12,7 @@ shortTitle: Teste do GitHub AE
 
 Você pode definir uma avaliação de 90 dias para avaliar {% data variables.product.prodname_ghe_managed %}. Este processo permite que você implemente uma conta do {% data variables.product.prodname_ghe_managed %} na sua região do Azure existente.
 
-- **Conta de {% data variables.product.prodname_ghe_managed %} **: O recurso do Azure que contém os componentes necessários, incluindo a instância.
+- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the deployment of {% data variables.product.prodname_ghe_managed %}.
 - **{% data variables.product.prodname_ghe_managed %} portal**: A ferramenta de gerenciamento do Azure em [https://portal.azure.com](https://portal.azure.com). Ela é usada para implantar a conta de {% data variables.product.prodname_ghe_managed %}.
 
 ## Configurar a versão de avaliação do {% data variables.product.prodname_ghe_managed %}
@@ -39,24 +39,24 @@ O endereço de e-mail que você digitou acima receberá instruções sobre como
 
 {% note %}
 
-**Observação:** As atualizações de software para a sua instância {% data variables.product.prodname_ghe_managed %} são executadas por {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte[Sobre atualizações para novas versões de](/admin/overview/about-upgrades-to-new-releases)."
+**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} deployment are performed by {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte[Sobre atualizações para novas versões de](/admin/overview/about-upgrades-to-new-releases)."
 
 {% endnote %}
 
 ## Acessando a sua empresa
 
-Você pode usar o {% data variables.actions.azure_portal %} para navegar para a sua instância de {% data variables.product.prodname_ghe_managed %}. A lista resultante inclui todas as instâncias de {% data variables.product.prodname_ghe_managed %} na sua região do Azure.
+You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} deployment. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} deployments in your Azure region.
 
 1. No {% data variables.actions.azure_portal %}, no painel esquerdo, clique em **Todos os recursos**.
 1. Nos filtros disponíveis, clique em **Todos os tipos** e, em seguida, desmarque **Selecionar todos** e selecione **GitHub AE**: ![Resultado da pesquisa de {% data variables.actions.azure_portal %}](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
 ## Próximas etapas
 
-Uma vez fornecida a sua instância, o próximo passo é para inicializar {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
+Once your deployment has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
 ## Finalizar a versão de avaliação
 
-Você pode fazer a atualização para uma licença completa a qualquer momento durante o período de avaliação, entrando em contato com {% data variables.contact.contact_enterprise_sales %}. Se você não atualizou até o último dia de seu teste, a instância será excluída automaticamente.
+Você pode fazer a atualização para uma licença completa a qualquer momento durante o período de avaliação, entrando em contato com {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the deployment is automatically deleted.
 
 Se precisar de mais tempo para avaliar o {% data variables.product.prodname_ghe_managed %}, entre em contato com {% data variables.contact.contact_enterprise_sales %} para solicitar uma extensão.
 
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index f5c9633c79..d0491e93f6 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -25,11 +25,9 @@ shortTitle: Enterprise Cloud trial
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
-{% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
 
-{% data reusables.enterprise-accounts.emu-short-summary %}
-
-{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
 
 {% data reusables.products.which-product-to-use %}
 
@@ -39,7 +37,11 @@ You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe
 
 Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
 
-Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
 
 ## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
 
@@ -62,11 +64,13 @@ After setting up your trial, you can explore {% data variables.product.prodname_
 
 ## Finishing your trial
 
-You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
 
-If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}. 
 
-Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
index 43b554c465..9c908949e3 100644
--- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md
+++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
@@ -26,10 +26,12 @@ A capacidade de executar comandos diretamente do seu teclado, sem navegar por me
 
 ## Abrindo o {% data variables.product.prodname_command_palette %}
 
-Abra a paleta de comandos usando um dos seguintes atalhos de teclado:
+Open the command palette using one of the following default keyboard shortcuts:
 - Windows e Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
 - Mac: <kbd>Command</kbd>+<kbd>K</kbd> ou <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
+You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)."
+
 Ao abrir a paleta de comando, ela mostra sua localização no canto superior esquerdo e a usa como o escopo de sugestões (por exemplo, a organização `mashed-avocado`).
 
 ![Lançamento da paleta de comando](/assets/images/help/command-palette/command-palette-launch.png)
@@ -42,6 +44,12 @@ Ao abrir a paleta de comando, ela mostra sua localização no canto superior esq
 
 {% endnote %}
 
+### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
+
+
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode.
+
+![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
 ## Navegando com {% data variables.product.prodname_command_palette %}
 
 Você pode usar a paleta de comandos para navegar para qualquer página que você tenha acesso em {% data variables.product.product_name %}.
@@ -96,7 +104,7 @@ Você pode usar o {% data variables.product.prodname_command_palette %} para exe
 
 Para obter uma lista completa dos comandos compatíveis, consulte "[Referência de {% data variables.product.prodname_command_palette %}](#github-command-palette-reference)".
 
-1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows e Linux) ou <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) para abrir a paleta de comandos no modo de comando. Se você já tiver a paleta de comandos aberta, pressione <kbd>></kbd> para alternar para o modo de comando. {% data variables.product.prodname_dotcom %} sugere comandos baseados na sua localização.
+1. The default keyboard shortcuts to open the command palette in command mode are <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac). Se você já tiver a paleta de comandos aberta, pressione <kbd>></kbd> para alternar para o modo de comando. {% data variables.product.prodname_dotcom %} sugere comandos baseados na sua localização.
 
    ![Modo de comando da paleta de comando](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -106,6 +114,7 @@ Para obter uma lista completa dos comandos compatíveis, consulte "[Referência
 
 4. Use as setas do teclado para destacar o comando que você deseja e use <kbd>Enter</kbd> para executá-lo.
 
+
 ## Fechando a paleta de comandos
 
 Quando a paleta de comando está ativa, você pode usar um dos seguintes atalhos de teclado para fechar a paleta de comandos:
@@ -113,6 +122,8 @@ Quando a paleta de comando está ativa, você pode usar um dos seguintes atalhos
 - Modo de pesquisa e navegação: <kbd>Esc</kbd> ou <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows e Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
 - Modo de comando: <kbd>Esc</kbd> ou <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows e Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.
+
 ## Referência de {% data variables.product.prodname_command_palette %}
 
 ### Funções de keystrokes
diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
index f68ee3e1e2..5336f9d287 100644
--- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
@@ -95,7 +95,8 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod
 | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 | <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | Insere a formatação Markdown para código ou um comando dentro da linha{% endif %}
 | <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | Insere formatação Markdown para criar um link                                                                                                                                                                                                                  |
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 | <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Insere a formatação de Markdown para uma lista ordenada                                                                                                                                                                                                        |
 | <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Insere a formatação Markdown para uma lista não ordenada{% endif %}
 | <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | Envia um comentário                                                                                                                                                                                                                                            |
@@ -105,6 +106,7 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod
 {% endif %}
 | <kbd>R</kbd>                                                                                                                  | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)".                                                                       |
 
+
 ## Listas de problemas e pull requests
 
 | Atalho                                                                                      | Descrição                                                                                                                                                                                                                                                        |
diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md
index db12e856e3..bef795a6f8 100644
--- a/translations/pt-BR/content/github/index.md
+++ b/translations/pt-BR/content/github/index.md
@@ -12,8 +12,6 @@ versions:
   ghae: '*'
 children:
   - /copilot
-  - /customizing-your-github-workflow
-  - /extending-github
   - /site-policy
   - /site-policy-deprecated
 ---
diff --git a/translations/pt-BR/content/issues/index.md b/translations/pt-BR/content/issues/index.md
index 5ba0b00aac..799e4b7a59 100644
--- a/translations/pt-BR/content/issues/index.md
+++ b/translations/pt-BR/content/issues/index.md
@@ -33,6 +33,7 @@ featuredLinks:
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
   videosHeading: GitHub Universe 2021 videos
+product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
 layout: product-landing
 beta_product: false
 versions:
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
index 5494704277..2bfa7f06da 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -76,5 +76,5 @@ Todos os problemas referenciados em uma lista de tarefas especificam que são ac
 
 ## Leia mais
 
-* "[Escrita básica e sintaxe de formatação](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Escrita básica e sintaxe de formatação](/articles/basic-writing-and-formatting-syntax)"{% if code-scanning-task-lists %}
 * "[Rastreando alertas de {% data variables.product.prodname_code_scanning %} em problemas que usam listas de tarefas](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 284e9dd2fb..0b73f71d50 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -143,7 +143,7 @@ Se você criar uma URL inválida usando parâmetros de consulta, ou se você nã
 | `projetos`            | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` cria um problema com o título "Correção de erro" e o adiciona ao quadro de projeto 1 da organização.                                                                                                                                                                                                                                                                                                       |
 | `modelo`              | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` cria um problema com um modelo no texto do problema. O parâmetro de consulta `template` funciona com modelos armazenados em um subdiretório `ISSUE_TEMPLATE` dentro da raiz, `docs/` ou diretório do `.github/` em um repositório. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". |
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Criando uma issue de um alerta de {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
index 57eafbdf8d..ff4e93a7c2 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
@@ -1,6 +1,6 @@
 ---
 title: Proteger sua organização
-intro: 'Os proprietários de organizações têm vários recursos disponíveis para ajudá-los a proteger seus projetos e dados. Se você for o proprietário de uma organização, você deverá revisar regularmente o log de auditoria da sua organização{% ifversion not ghae %}, status de 2FA do integrante{% endif %} e as configurações do aplicativo para garantir que não ocorra nenhuma atividade não autorizada ou maliciosa.'
+intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -14,14 +14,8 @@ topics:
   - Organizations
   - Teams
 children:
-  - /viewing-whether-users-in-your-organization-have-2fa-enabled
-  - /preparing-to-require-two-factor-authentication-in-your-organization
-  - /requiring-two-factor-authentication-in-your-organization
-  - /managing-security-and-analysis-settings-for-your-organization
-  - /managing-allowed-ip-addresses-for-your-organization
-  - /restricting-email-notifications-for-your-organization
-  - /reviewing-the-audit-log-for-your-organization
-  - /reviewing-your-organizations-installed-integrations
+  - /managing-two-factor-authentication-for-your-organization
+  - /managing-security-settings-for-your-organization
 shortTitle: Segurança da organização
 ---
 
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
new file mode 100644
index 0000000000..6196197d3e
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your organization
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Teams
+permissions: Organization owners can access compliance reports for the organization.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "Compliance reports", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Leia mais
+
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
new file mode 100644
index 0000000000..6c813260f9
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing security settings for your organization
+shortTitle: Manage security settings
+intro: 'You can manage security settings and review the audit log{% ifversion ghec %}, compliance reports,{% endif %} and integrations for your organization.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-security-and-analysis-settings-for-your-organization
+  - /managing-allowed-ip-addresses-for-your-organization
+  - /restricting-email-notifications-for-your-organization
+  - /reviewing-the-audit-log-for-your-organization
+  - /accessing-compliance-reports-for-your-organization
+  - /reviewing-your-organizations-installed-integrations
+---
+
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
new file mode 100644
index 0000000000..dc77352b83
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -0,0 +1,85 @@
+---
+title: Gerenciar endereços IP permitidos para sua organização
+intro: Você pode restringir o acesso aos ativos da sua organização configurando uma lista de endereços IP autorizados a se conectar.
+product: '{% data reusables.gated-features.allowed-ip-addresses %}'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Gerenciar endereços IP permitidos
+---
+
+Os proprietários da organização podem gerenciar endereços IP permitidos para uma organização.
+
+## Sobre endereços IP permitidos
+
+Você pode restringir o acesso a ativos da organização configurando uma lista de permissões para endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
+
+Se você configurar uma lista de permissões, você também poderá optar por adicionar automaticamente à sua lista de permissões todos os endereços IP configurados em {% data variables.product.prodname_github_apps %} que você instalar na sua organização. O criador de um {% data variables.product.prodname_github_app %} pode configurar uma lista de permissões para o seu aplicativo, especificando os endereços IP em que o aplicativo é executado. Ao herdar a lista de permissões deles para a sua lista, você evita as solicitações de conexão do aplicativo que está sendo recusado. Para obter mais informações, consulte "[Permitir acesso por {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)".
+
+Você também pode configurar endereços IP permitidos para as organizações em uma conta corporativa. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
+
+## Adicionar endereços IP permitidos
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+
+## Habilitar endereços IP permitidos
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Em "IP allow list" (Lista de permissões IP), selecione **Enable IP allow list** (Habilitar lista de permissões IP). ![Caixa de seleção para permitir endereços IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. Clique em **Salvar**.
+
+## Permitindo acesso de {% data variables.product.prodname_github_apps %}
+
+Se você estiver usando uma lista de permissão, você também pode optar por adicionar automaticamente à sua lista de permissões todos os endereços IP configurados em {% data variables.product.prodname_github_apps %} que você instalar na sua organização.
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+Para mais informações sobre como criar uma lista de permissões para uma {% data variables.product.prodname_github_app %} que você criou, consulte "[Gerenciar endereços IP permitidos para um aplicativo GitHub](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Em "Lista de permissão do IP", selecione **Habilitar o IP para a configuração da lista de aplicativos instalados no GitHub**. ![Caixa de seleção para permitir endereços IP do aplicativo GitHub](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Clique em **Salvar**.
+
+## Editar endereços IP permitidos
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+1. Clique em **Atualizar**.
+
+## Excluir endereços IP permitidos
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
+
+{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
new file mode 100644
index 0000000000..9212aa7ad9
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -0,0 +1,171 @@
+---
+title: Gerenciar as configurações de segurança e análise para a sua organização
+intro: 'Você pode controlar recursos que protegem e analisam o código nos projetos da sua organização no {% data variables.product.prodname_dotcom %}.'
+permissions: Organization owners can manage security and analysis settings for repositories in the organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Gerenciar segurança & análise
+---
+
+## Sobre a gestão de configurações de segurança e análise
+
+O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. {% ifversion ghec %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, você também poderá gerenciar o acesso a essas funcionalidades. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizações que usam {% data variables.product.prodname_ghe_cloud %} com uma licença para {% data variables.product.prodname_GH_advanced_security %} também podem gerenciar o acesso a essas funcionalidades. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## Exibir as configurações de segurança e análise
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+
+A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização.
+
+{% ifversion ghec %}Se a sua organização pertence a uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
+
+{% ifversion ghes > 3.0 %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
+
+{% ifversion ghae %}A página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
+
+## Habilitar ou desabilitar um recurso para todos os repositórios existentes
+
+Você pode habilitar ou desabilitar funcionalidades para todos os repositórios.
+{% ifversion fpt or ghec %}O impacto de suas alterações nos repositórios da organização é determinado pela visibilidade:
+
+- **Gráfico de dependências** - Suas alterações afetam apenas repositórios privados porque a funcionalidade está sempre habilitada para repositórios públicos.
+- **{% data variables.product.prodname_dependabot_alerts %}** - As suas alterações afetam todos os repositórios.
+- **{% data variables.product.prodname_dependabot_security_updates %}** - As suas alterações afetam todos os repositórios.
+{%- ifversion ghec %}
+- **{% data variables.product.prodname_GH_advanced_security %}** - As suas alterações afetam apenas repositórios privados, porque {% data variables.product.prodname_GH_advanced_security %} e os as funcionalidades relacionadas estão sempre habilitadas para repositórios públicos.
+- **{% data variables.product.prodname_secret_scanning_caps %}** - As suas alterações afetam apenas repositórios privados em que {% data variables.product.prodname_GH_advanced_security %} também está habilitado. {% data variables.product.prodname_secret_scanning_caps %} está sempre habilitado para repositórios públicos.
+{% endif %}
+
+{% endif %}
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
+2. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. {% ifversion ghes > 3.0 or ghec %}O controle para "{% data variables.product.prodname_GH_advanced_security %}" fica desabilitado se você não tiver estações disponíveis na sua licença de {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
+   {% ifversion fpt %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   {% endif %}
+   {% ifversion ghes > 3.2 %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão.
+   {% ifversion fpt or ghec %}
+   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+4. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização.
+   {% ifversion fpt or ghec %}
+   ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Botão para desabilitar ou habilitar recurso](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion ghae or ghes > 3.0 %}
+3. Clique em **Habilitar/Desabilitar todos** ou **Habilitar/Desabilitar para repositórios elegíveis** para confirmar a alteração. ![Botão para habilitar o recurso para todos os repositórios elegíveis na organização](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% endif %}
+
+   {% data reusables.security.displayed-information %}
+
+## Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados
+
+1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
+2. Em "Configurar funcionalidades de segurança e análise", à direita da funcionalidade, habilite ou desabilite o recurso por padrão para novos repositórios{% ifversion fpt or ghec %}, ou todos os novos repositórios privados,{% endif %} na sua organização.
+   {% ifversion fpt %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   {% endif %}
+
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
+
+## Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas
+
+{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso a todos os arquivos de dependência de destino. Normalmente, atualizações da versão irão falhar se uma ou mais dependências forem inacessíveis. Para obter mais informações, consulte "[Sobre atualizações da versão de {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)".
+
+Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências que estão localizadas em repositórios privados ou registros de pacotes privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório.
+
+Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)".
+
+Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}:
+
+1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
+1. Em "Acesso ao repositório privado de {% data variables.product.prodname_dependabot %}", clique em **Adicionar repositórios privados** ou **Adicionar repositórios internos e privados**. ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. Comece a digitar o nome do repositório que você deseja permitir. ![Campo de pesquisa do repositório com menu suspenso filtrado](/assets/images/help/organizations/dependabot-private-repo-choose.png)
+1. Clique no repositório que você deseja permitir.
+
+1. Opcionalmente, para remover um repositório da lista, à direita do repositório, clique em {% octicon "x" aria-label="The X icon" %}. ![Botão "X" para remover um repositório](/assets/images/help/organizations/dependabot-private-repository-list.png)
+{% endif %}
+
+{% ifversion ghes > 3.0 or ghec %}
+
+## Remover acesso a {% data variables.product.prodname_GH_advanced_security %} de repositórios individuais em uma organização
+
+Você pode gerenciar o acesso a funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações". Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". No entanto, você também pode desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações" da organização.
+
+1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
+1. Para ver uma lista de todos os repositórios na sua organização com {% data variables.product.prodname_GH_advanced_security %} habilitados, desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) A tabela lista o número de committers únicos para cada repositório. Este é o número de estações que você poderia liberar em sua licença, removendo acesso a {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".
+1. Para remover acesso ao {% data variables.product.prodname_GH_advanced_security %} de um repositório e liberar estações usadas por todos os committers que são exclusivos do repositório, clique no {% octicon "x" aria-label="X symbol" %} adjacente.
+1. Na caixa de diálogo de confirmação, clique em **Remover repositório** para remover acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %}.
+
+{% note %}
+
+**Observação:** Se você remover o acesso a {% data variables.product.prodname_GH_advanced_security %} para um repositório, você deverá comunicar-se com a equipe de desenvolvimento afetada para que saibam que a alteração foi planejada. Isso garante que eles não perderão tempo corrigindo execuções falhas de varredura de código.
+
+{% endnote %}
+
+{% endif %}
+
+## Leia mais
+
+- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[Sobre a verificação de segredo](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Gerenciar vulnerabilidades nas dependências do seu projeto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Manter suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..6070cc6339
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,47 @@
+---
+title: Restringir notificações de e-mail para sua organização
+intro: 'Para evitar que as informações da organização sejam divulgadas para contas pessoais de e-mail, você pode restringir domínios em que os integrantes podem receber notificações de e-mail sobre a atividade da organização.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '>=3.2'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: Restringir notificações de e-mail
+---
+
+## Sobre restrições de e-mail
+
+Quando as notificações de e-mail restritas são habilitadas em uma organização, os integrantes só podem usar um endereço de e-mail associado a um domínio verificado ou aprovado para receber as notificações de e-mail sobre a atividade da organização. Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua organização](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Os colaboradores externos não estão sujeitos às restrições de notificações por e-mail para domínios verificados ou aprovados. Para obter mais informações sobre colaboradores externos, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
+
+Se sua organização pertence a uma conta corporativa os integrantes da organização poderão receber notificações de qualquer domínio verificado ou aprovado para a conta corporativa, Além de quaisquer domínios verificados ou aprovados para a organização. Para obter mais informações, consulte "[Verificando ou aprovando um domínio para sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
+
+## Restringir notificações de e-mail
+
+Antes de restringir as notificações de e-mail para a sua organização, você deve verificar ou aprovar pelo menos um domínio para a organização ou o proprietário da empresa deve ter verificado ou aprovado pelo menos um domínio para a conta corporativa.
+
+Para obter mais informações sobre verificações e aprovações de domínios para uma organização, consulte "[Verificar ou aprovar um domínio para a sua organização](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
new file mode 100644
index 0000000000..00ff2830cb
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -0,0 +1,770 @@
+---
+title: Reviewing the audit log for your organization
+intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-the-audit-log-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization
+  - /organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Review audit log
+---
+
+## Accessing the audit log
+
+The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+
+## Searching the audit log
+
+{% data reusables.audit_log.audit-log-search %}
+
+### Search based on the action performed
+
+To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories:
+
+| Category name | Description
+|------------------|-------------------{% ifversion fpt or ghec %}
+| [`account`](#account-category-actions) | Contains all activities related to your organization account.
+| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.
+| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
+| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
+| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
+| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page.
+| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
+| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %}
+| [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
+| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |
+| [`ip_allow_list`](#ip_allow_list) | Contains activities related to enabling or disabling the IP allow list for an organization.
+| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
+| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% ifversion fpt or ghec %}
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
+| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %}
+| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
+| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %}
+| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}
+| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture.
+| [`project`](#project-category-actions) | Contains all activities related to project boards.
+| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches.
+| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %}
+| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}.  For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
+| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
+| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
+| [`team`](#team-category-actions) | Contains all activities related to teams in your organization.
+| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| [`workflows`](#workflows-category-actions) | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %}
+
+You can search for specific sets of actions using these terms. For example:
+
+  * `action:team` finds all events grouped within the team category.
+  * `-action:hook` excludes all events in the webhook category.
+
+Each category has a set of associated actions that you can filter on. For example:
+
+  * `action:team.create` finds all events where a team was created.
+  * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered.
+
+### Search based on time of action
+
+Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+For example:
+
+  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
+  * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
+  * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
+  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+
+
+{% note %}
+
+**Note**: The audit log contains data for the current month and every day of the previous six months.
+
+{% endnote %}
+
+### Search based on location
+
+Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:
+
+  * `country:de` finds all events that occurred in Germany.
+  * `country:Mexico` finds all events that occurred in Mexico.
+  * `country:"United States"` all finds events that occurred in the United States.
+
+{% ifversion fpt or ghec %}
+## Exporting the audit log
+
+{% data reusables.audit_log.export-log %}
+{% data reusables.audit_log.exported-log-keys-and-values %}
+{% endif %}
+
+## Using the audit log API
+
+You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.
+
+{% ifversion fpt or ghec %}
+The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+
+### Using the GraphQL API
+
+{% endif %}
+
+{% note %}
+
+**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %}
+
+{% endnote %}
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audit-log-api-info %}
+
+{% ifversion fpt or ghec %}
+Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)."
+{% endif %}
+
+The GraphQL response can include data for up to 90 to 120 days.
+
+For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)."
+
+{% ifversion fpt or ghec %}
+
+### Using the REST API
+
+{% note %}
+
+**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only.
+
+{% endnote %}
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+{% endif %}
+
+## Audit log actions
+
+An overview of some of the most common actions that are recorded as events in the audit log.
+
+{% ifversion fpt or ghec %}
+### `account` category actions
+
+| Action | Description
+|------------------|-------------------
+| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes.
+| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes.
+| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/).
+| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/).
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `advisory_credit` category actions
+
+| Action | Description
+|------------------|-------------------
+| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)."
+| `create` | Triggered when the administrator of a security advisory adds someone to the credit section.
+| `decline` | Triggered when someone declines credit for a security advisory.
+| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `billing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method).
+| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes.
+{% endif %}
+
+### `business` category actions
+
+| Action | Description
+|------------------|-------------------{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on  private repository forks is changed. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %}
+
+{% ifversion fpt or ghec %}
+### `codespaces` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
+| `resume` | Triggered when a user resumes a suspended codespace.
+| `delete` | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
+| `create_an_org_secret` | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)
+| `update_an_org_secret` | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `remove_an_org_secret` | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.2 %}
+### `dependabot_alerts` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+### `dependabot_alerts_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+### `dependabot_security_updates` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories.
+
+### `dependabot_security_updates_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `dependency_graph` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories.
+
+### `dependency_graph_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories.
+{% endif %}
+
+### `discussion_post` category actions
+
+| Action | Description
+|------------------|-------------------
+| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
+| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
+
+### `discussion_post_reply` category actions
+
+| Action | Description
+|------------------|-------------------
+| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
+| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
+
+{% ifversion fpt or ghes or ghec %}
+### `enterprise` category actions
+
+{% data reusables.actions.actions-audit-events-for-enterprise %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `environment` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)."
+| `remove_actions_secret` |  Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+{% endif %}
+
+{% ifversion ghae %}
+### `external_group` category actions
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% endif %}
+
+{% ifversion ghae %}
+### `external_identity` category actions
+
+{% data reusables.saml.external-identity-audit-events %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `git` category actions
+
+{% note %}
+
+**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+{% endnote %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+| Action  | Description
+|---------|----------------------------
+| `clone` | Triggered when a repository is cloned.
+| `fetch` | Triggered when changes are fetched from a repository.
+| `push`  | Triggered when changes are pushed to a repository.
+
+{% endif %}
+
+### `hook` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization.
+| `config_changed` | Triggered when an existing hook has its configuration altered.
+| `destroy` | Triggered when an existing hook was removed from a repository.
+| `events_changed` | Triggered when the events on a hook have been altered.
+
+### `integration_installation_request` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization.
+| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request.
+
+### `ip_allow_list` category actions
+
+| Action | Description
+|------------------|-------------------
+| `enable` | Triggered when an IP allow list was enabled for an organization.
+| `disable` | Triggered when an IP allow list was disabled for an organization.
+| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
+| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+
+### `ip_allow_list_entry` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when an IP address was added to an IP allow list.
+| `update` | Triggered when an IP address or its description was changed.
+| `destroy` | Triggered when an IP address was deleted from an IP allow list.
+
+### `issue` category actions
+
+| Action | Description
+|------------------|-------------------
+| `destroy`        | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository.
+
+{% ifversion fpt or ghec %}
+
+### `marketplace_agreement_signature` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+
+### `marketplace_listing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
+| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
+| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
+| `redraft` | Triggered when your listing is sent back to draft state.
+| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+
+{% endif %}
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+
+### `members_can_create_pages` category actions
+
+For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+
+| Action | Description |
+| :- | :- |
+| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. |
+| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. |
+
+{% endif %}
+
+### `org` category actions
+
+| Action | Description
+|------------------|-------------------
+| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %}
+| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query.
+| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).
+| `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %}
+| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %}
+| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %}
+| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization).
+| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/).
+| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization.
+| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}
+| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."
+| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %}
+| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %}
+| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.|
+| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |
+| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion ghec %}
+| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."
+| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %}
+| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."
+| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).
+| `runner_group_runner_removed` |  Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."
+| `runner_group_runners_updated`|  Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on  private repository forks is changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %}
+| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}
+| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."
+| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members.
+| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner.
+| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %}
+| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated.
+| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %}
+
+{% ifversion ghec %}
+### `org_credential_authorization` category actions
+
+| Action | Description
+|------------------|-------------------
+| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).
+| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).
+| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization).
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghae or ghec %}
+### `organization_label` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a default label is created.
+| `update` | Triggered when a default label is edited.
+| `destroy` | Triggered when a default label is deleted.
+
+{% endif %}
+
+### `oauth_application` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created.
+| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted.
+| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset.
+| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked.
+| `transfer` |  Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization.
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+### `packages` category actions
+
+| Action | Description |
+|--------|-------------|
+| `package_version_published` | Triggered when a package version is published. |
+| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `payment_method` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
+| `update` | Triggered when an existing payment method is updated.
+
+{% endif %}
+
+### `profile_picture` category actions
+| Action | Description
+|------------------|-------------------
+| update | Triggered when you set or update your organization's profile picture.
+
+### `project` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `create` | Triggered when a project board is created.
+| `link` | Triggered when a repository is linked to a project board.
+| `rename` | Triggered when a project board is renamed.
+| `update` | Triggered when a project board is updated.
+| `delete` | Triggered when a project board is deleted.
+| `unlink` | Triggered when a repository is unlinked from a project board.
+| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. |
+| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. |
+| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.|
+
+### `protected_branch` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `create ` | Triggered when branch protection is enabled on a branch.
+| `destroy` | Triggered when branch protection is disabled on a branch.
+| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators.
+| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
+| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
+| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
+| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
+| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
+| `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
+| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %}
+| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch.
+| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch.
+| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch.
+{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+
+### `pull_request` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a pull request is created.
+| `close` | Triggered when a pull request is closed without being merged.
+| `reopen` | Triggered when a pull request is reopened after previously being closed.
+| `merge` | Triggered when a pull request is merged.
+| `indirect_merge` | Triggered when a pull request is considered merged because its commits were merged into the target branch.
+| `ready_for_review` | Triggered when a pull request is marked as ready for review.
+| `converted_to_draft` | Triggered when a pull request is converted to a draft.
+| `create_review_request` | Triggered when a review is requested.
+| `remove_review_request` | Triggered when a review request is removed.
+
+### `pull_request_review` category actions
+
+| Action | Description
+|------------------|-------------------
+| `submit` | Triggered when a review is submitted.
+| `dismiss` | Triggered when a review is dismissed.
+| `delete` | Triggered when a review is deleted.
+
+### `pull_request_review_comment` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a review comment is added.
+| `update` | Triggered when a review comment is changed.
+| `delete` | Triggered when a review comment is deleted.
+
+{% endif %}
+
+### `repo` category actions
+
+| Action | Description
+|------------------|-------------------
+| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization.
+| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)."
+| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository).
+| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %}
+| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
+| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %}
+| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}
+| `enable` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %}
+| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}
+| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
+| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."
+| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."
+| `remove_topic` | Triggered when a repository admin removes a topic from a repository.
+| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
+| `transfer_start` | Triggered when a repository transfer is about to occur.
+| `unarchived` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `repository_advisory` category actions
+
+| Action | Description
+|------------------|-------------------
+| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.
+| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}.
+| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error.
+| `open` | Triggered when someone opens a draft security advisory.
+| `publish` | Triggered when someone publishes a security advisory.
+| `reopen` | Triggered when someone reopens as draft security advisory.
+| `update` | Triggered when someone edits a draft or published security advisory.
+
+### `repository_content_analysis` category actions
+
+| Action | Description
+|------------------|-------------------
+| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+
+{% endif %}{% ifversion fpt or ghec %}
+
+### `repository_dependency_graph` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository.
+
+{% endif %}{% ifversion ghec or ghes or ghae %}
+### `repository_secret_scanning` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository.
+
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+### `repository_vulnerability_alert` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency.
+| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.
+
+{% endif %}{% ifversion fpt or ghec %}
+### `repository_vulnerability_alerts` category actions
+
+| Action | Description
+|------------------|-------------------
+| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}.
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}.
+
+{% endif %}{% ifversion ghec %}
+### `role` category actions
+| Action | Description
+|------------------|-------------------
+|`create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+### `secret_scanning` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.
+
+### `secret_scanning_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `sponsors` category actions
+
+| Action | Description
+|------------------|-------------------
+| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
+| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
+| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
+| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
+| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
+| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")
+| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
+| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")
+| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+{% endif %}
+
+### `team` category actions
+
+| Action | Description
+|------------------|-------------------
+| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team).
+| `add_repository` | Triggered when a team is given control of a repository.
+| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy).
+| `change_privacy` | Triggered when a team's privacy level is changed.
+| `create` | Triggered when a new team is created.
+| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."
+| `destroy` | Triggered when a team is deleted from the organization.
+| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."
+| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team).
+| `remove_repository` | Triggered when a repository is no longer under a team's control.
+
+### `team_discussions` category actions
+
+| Action | Description
+|---|---|
+| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)."
+| `enable` | Triggered when an organization owner enables team discussions for an organization.
+
+{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### `workflows` category actions
+
+{% data reusables.actions.actions-audit-events-workflow %}
+{% endif %}
+## Further reading
+
+- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
new file mode 100644
index 0000000000..96869d9fe2
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -0,0 +1,31 @@
+---
+title: Revisar as integrações instaladas da organização
+intro: Você pode revisar os níveis de permissão das integrações instaladas da organização e configurar o acesso de cada integração aos repositórios da organização.
+redirect_from:
+  - /articles/reviewing-your-organization-s-installed-integrations
+  - /articles/reviewing-your-organizations-installed-integrations
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations
+  - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Revisar integrações instaladas
+---
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
+{% elsif ghae or ghes < 3.4 %}
+1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_github_apps %} instalado**. ![Aba de {% data variables.product.prodname_github_apps %} instalada na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-installed-github-apps.png)
+{% endif %}
+2. Próximo do {% data variables.product.prodname_github_app %} que deseja revisar, clique em **Configure** (Configurar). ![Botão Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png)
+6. Revise o acesso ao repositório e as permissões de {% data variables.product.prodname_github_app %}. ![Opção para fornecer ao {% data variables.product.prodname_github_app %} acesso a todos os repositórios ou a repositórios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png)
+    - Para fornecer acesso ao {% data variables.product.prodname_github_app %} em todos os repositórios da organização, selecione **All repositories** (Todos os repositórios).
+    - Para selecionar repositórios específicos para fornecer acesso ao aplicativo, selecione **Only select repositories** (Somente os repositórios selecionados) e insira o nome do repositório.
+7. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
new file mode 100644
index 0000000000..df495a0d4f
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -0,0 +1,17 @@
+---
+title: Managing two-factor authentication for your organization
+shortTitle: Manage 2FA
+intro: You can view whether users with access to your organization have two-factor authentication (2FA) enabled and require 2FA.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /preparing-to-require-two-factor-authentication-in-your-organization
+  - /requiring-two-factor-authentication-in-your-organization
+---
+
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..ef40c0a0f2
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: Preparar para exigir autenticação de dois fatores na organização
+intro: 'Antes de exigir autenticação de dois fatores (2FA), é possível notificar os usuários sobre as próximas mudanças e verificar quem já utiliza 2FA.'
+redirect_from:
+  - /articles/preparing-to-require-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Prepare-se para exigir 2FA
+---
+
+Recomendamos que você notifique os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança da organização{% else %}integrantes e colaboradores externos da organização{% endif %} no mínimo uma semana antes de você exigir a 2FA na organização.
+
+Se você exigir o uso da autenticação de dois fatores na organização, os integrantes, colaboradores externos e gerentes de cobrança (inclusive contas bots) que não usam 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização.
+
+Antes de exigir 2FA na organização, recomendamos que você:
+  - [Habilite a 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) em sua conta pessoal
+  - Solicite às pessoas da organização para configurar 2FA na conta delas
+  - Verifique se [os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/)
+  - Alerte os usuários que assim que a 2FA estiver habilitada, aqueles que não a tiverem habilitado serão automaticamente removidos da organização
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..97c31db352
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Exigir autenticação de dois fatores em sua organização
+intro: 'Os proprietários da organização podem exigir que os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança da organização{% else %}integrantes e colaboradores externos da organização{% endif %} habilitem a autenticação de dois fatores em suas contas pessoais para dificultar o acesso aos repositórios e às configurações da organização.'
+redirect_from:
+  - /articles/requiring-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Exigir 2FA
+---
+
+## Sobre a autenticação de dois fatores para organizações
+
+{% data reusables.two_fa.about-2fa %} Você pode exigir que todos os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança {% else %}integrantes e colaboradores externos na sua organização{% endif %} habilitem a autenticação de dois fatores em {% data variables.product.product_name %}. Para obter mais informações sobre a autenticação de dois fatores, consulte "[Proteger a sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
+
+{% ifversion fpt or ghec %}
+
+Você também pode exigir autenticação de dois fatores para as organizações de uma empresa. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
+
+{% endif %}
+
+{% warning %}
+
+**Avisos:**
+
+- Se você exigir o uso da autenticação de dois fatores na organização, os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança{% else %}integrantes e colaboradores externos{% endif %} da sua organização (incluindo contas bot) que não usam a 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização. Se eles habilitarem a autenticação de dois fatores for habilitada na conta pessoal em até três meses após a remoção da organização, você poderá [restabelecer as configurações e os privilégios de acesso deles](/articles/reinstating-a-former-member-of-your-organization).
+- Se um proprietário, integrante,{% ifversion fpt or ghec %} gerente de cobrança{% endif %} ou colaborador externo da organização desabilitar a 2FA em sua conta pessoal depois que você tiver habilitado a autenticação de dois fatores obrigatória, ele será automaticamente removido da organização.
+- Se você for o único proprietário de uma organização que exige autenticação de dois fatores, não poderá desabilitar a 2FA na sua conta pessoal sem desabilitar a autenticação de dois fatores obrigatória na organização.
+
+{% endwarning %}
+
+{% data reusables.two_fa.auth_methods_2fa %}
+
+## Pré-requisitos
+
+Antes de poder exigir que {% ifversion fpt or ghec %}os integrantes da organização, colaboradores externos e gerentes de cobrança{% else %}integrantes da organização e colaboradores externos{% endif %} usem a autenticação de dois fatores, você deve habilitá-la para a sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Proteger sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
+
+Antes de exigir o uso da autenticação de dois fatores, recomendamos que você notifique os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança da organização{% else %}integrantes e colaboradores externos da organização{% endif %} e peça para eles configurarem a 2FA nas contas deles. Você pode ver se os integrantes e colaboradores externos já estão usando a 2FA. Para obter mais informações, consulte "[Ver se os usuários na organização têm a 2FA habilitada](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)".
+
+## Exigir autenticação de dois fatores em sua organização
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+{% ifversion fpt or ghec %}
+8. Se algum integrante ou colaborador externo for removido da organização, recomendamos o envio de um convite para restabelecer os privilégios e o acesso à organização que ele tinha anteriormente. O usuário precisa habilitar a autenticação de dois fatores para poder aceitar o convite.
+{% endif %}
+
+## Exibir pessoas removidas da organização
+
+Para exibir as pessoas que foram removidas automaticamente da organização por motivo de não conformidade quando você passou a exibir a autenticação de dois fatores, você pode [pesquisar o log de auditoria da organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) para consultar as pessoas removidas da organização. O evento do log de auditoria mostrará se uma pessoa foi removida por motivo de não conformidade com a 2FA.
+
+![Evento do log de auditoria mostrando um usuário removido por motivo de não conformidade com a 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+4. Faça a pesquisa. Para pesquisar:
+    - Integrantes da organização removidos, use `action:org.remove_member` na pesquisa
+    - Colaboradores externos removidos, use `action:org.remove_outside_collaborator` na pesquisa{% ifversion fpt or ghec %}
+    - Gerentes de cobrança removidos, use `action:org.remove_billing_manager`na pesquisa{% endif %}
+
+ Você também pode exibir as pessoas que foram removidas da organização usando um [intervalo de tempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) na pesquisa.
+
+## Ajudar integrantes e colaboradores externos removidos a voltarem à organização
+
+Se algum integrante ou colaborador externo for removido da organização quando você habilitar o uso obrigatório da autenticação de dois fatores, o integrante/colaborador receberá um e-mail informando que foi removido. Para solicitar acesso à sua organização, o integrante/colaborador deverá ativar a 2FA na conta pessoal e entrar em contato com o proprietário da organização.
+
+## Leia mais
+
+- "[Ver se os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Proteger sua conta com autenticação de dois fatores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)"
+- "[Restabelecer o acesso de um ex-colaborador externo à organização](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
new file mode 100644
index 0000000000..7712d4b872
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -0,0 +1,33 @@
+---
+title: Ver se os usuários da organização habilitaram a 2FA
+intro: 'Você pode ver quais proprietários da organização, integrantes e colaboradores externos habilitaram a autenticação de dois fatores.'
+redirect_from:
+  - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View 2FA usage
+---
+
+{% note %}
+
+**Observação:** você pode exigir que todos os integrantes{% ifversion fpt or ghec %}, inclusive proprietários, gerentes de cobrança e{% else %} e{% endif %} colaboradores externos na sua organização tenham a autenticação de dois fatores habilitada. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/articles/requiring-two-factor-authentication-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. Para exibir os integrantes da organização, inclusive proprietários da organização, que habilitaram ou desabilitaram a autenticação de dois fatores, clique em **2FA** à direita e selecione **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png)
+5. Clique em **Outside collaborators** (Colaboradores externos), na guia "People" (Pessoas), para exibir aqueles que pertencem à sua organização. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png)
+6. Para exibir quais colaboradores externos habilitaram ou desabilitaram a autenticação de dois fatores, clique em **2FA** à direita e selecione **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
+
+## Leia mais
+
+- "[Exibir as funções das pessoas em uma organização](/articles/viewing-people-s-roles-in-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 79965523a7..d15885bb89 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -23,6 +23,7 @@ Se você permitir a bifurcação de repositórios privados{% ifversion ghes or g
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
 1. Em "Bifurcação de repositório", selecione **Permitir bifurcação de repositórios {% ifversion ghec or ghes or ghae %}privados e {% endif %}internos**.
 
    {%- ifversion fpt %}
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index 638d14916e..46a3f4fec0 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -90,6 +90,8 @@ Você só pode escolher uma permissão adicional se já não estiver incluída n
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
 - **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts.
+- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}.
+- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}.
 - **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts.
 
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index daaf4cc5c2..6ad3762ee5 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -23,7 +23,7 @@ Também é possível verificar um domínio para sua organização{% ifversion gh
 ## Verificando um domínio para o seu site de usuário
 
 {% data reusables.user_settings.access_settings %}
-1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Opção Páginas no menu de configurações](/assets/images/help/settings/user-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Aguarde que a configuração de DNS seja alterada. Isto pode ser imediato ou demorar até 24 horas. Você pode confirmar a alteração na configuração do seu DNS executando o comando `dig` na linha de comando. No comando abaixo, substitua `USUÁRIO` pelo seu nome de usuário e `example.com` pelo domínio que você está verificando. Se a sua configuração de DNS foi atualizada, você deverá ver o seu novo registro TXT na saída.
   ```
@@ -37,7 +37,7 @@ Os proprietários da organização podem verificar domínios personalizados para
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Opção Páginas no menu de configurações](/assets/images/help/settings/org-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Aguarde que a configuração de DNS seja alterada. Isto pode ser imediato ou demorar até 24 horas. Você pode confirmar a alteração na configuração do seu DNS executando o comando `dig` na linha de comando. No comando abaixo, substitua `ORGANIZAÇÃO` pelo nome da sua organização e `example.com` pelo domínio que você está verificando. Se a sua configuração de DNS foi atualizada, você deverá ver o seu novo registro TXT na saída.
   ```
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index 4956af9768..b0a53a967d 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -162,6 +162,7 @@ Para obter mais informações sobre a criação de pull requests em {% data vari
 ## Leia mais
 
 - "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)"
 - "[Alterar o branch base de uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)"
 - "[Adicionar problemas e pull requests a um quadro de projeto da barra lateral](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)"
 - "[Sobre automação de problemas e pull requests com parâmetros de consulta](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 6817bf2727..e6afeb715d 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -22,6 +22,7 @@ children:
   - /using-query-parameters-to-create-a-pull-request
   - /changing-the-stage-of-a-pull-request
   - /requesting-a-pull-request-review
+  - /keeping-your-pull-request-in-sync-with-the-base-branch
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
 shortTitle: Propor alterações
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
new file mode 100644
index 0000000000..650aadcc3d
--- /dev/null
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
@@ -0,0 +1,53 @@
+---
+title: Keeping your pull request in sync with the base branch
+intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.'
+permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Update the head branch
+---
+
+## About keeping your pull request in sync
+
+Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging.
+
+You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true:
+
+* There are no merge conflicts between the pull request branch and the base branch.
+* The pull request branch is not up to date with the base branch.
+* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} or the setting to always suggest updating branches is enabled{% endif %}.
+
+For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}" and "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}."
+
+If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)."
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created.
+{% else %}
+Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request.
+{% endif %}
+
+## Updating your pull request branch
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull requests" list, click the pull request you'd like to update.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+1. In the merge section near the bottom of the page, you can:
+   - Click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png)
+   - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch. ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png)
+{% else %}
+1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch.png)
+{% endif %}
+
+## Leia mais
+
+- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)"
+- "[Fazer commit de alterações em um branch da pull request criado de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
index 49f3c23dba..ff01250967 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
@@ -19,4 +19,4 @@ shortTitle: Configurar rebase de commit
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Abaixo do "Merge button" (botão Fazer merge), selecione **Allow rebase merging** (Permitir merge do rebase). Isso permite que os contribuidores façam merge de uma pull request fazendo rebase dos respectivos commits individuais no branch base. Se você também selecionar outro método de merge, os colaboradores poderão escolher o tipo de commit do merge ao fazer merge de uma pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Commits com rebase da pull request](/assets/images/help/repository/pr-merge-rebase.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. Isso permite que os contribuidores façam merge de uma pull request fazendo rebase dos respectivos commits individuais no branch base. Se você também selecionar outro método de merge, os colaboradores poderão escolher o tipo de commit do merge ao fazer merge de uma pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Commits com rebase da pull request](/assets/images/help/repository/pr-merge-rebase.png)
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index ab3a0b9e12..934e74f287 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -21,8 +21,8 @@ shortTitle: Configurar combinação por squash de commit
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Abaixo do "Merge button" (botão Fazer merge), se desejar, selecione **Allow merge commits** (Permitir commits de merge). Isso permite que os contribuidores façam merge de uma pull request com um histórico completo de commits. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. Abaixo do "Merge button" (botão Fazer merge), selecione **Allow squash merging** (Permitir merge de combinação por squash). Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. Se você selecionar outro método além de **Allow squash merging** (Permitir merge de combinação por squash), os colaboradores poderão escolher o tipo de commit do merge ao fazer merge de uma pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Commits de combinação por squash da pull request](/assets/images/help/repository/pr-merge-squash.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. Isso permite que os contribuidores façam merge de uma pull request com um histórico completo de commits. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
+4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. Se você selecionar outro método além de **Allow squash merging** (Permitir merge de combinação por squash), os colaboradores poderão escolher o tipo de commit do merge ao fazer merge de uma pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Commits de combinação por squash da pull request](/assets/images/help/repository/pr-merge-squash.png)
 
 ## Leia mais
 
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
index b45d43ac5b..1ae9d3859a 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -16,6 +16,7 @@ children:
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
   - /using-a-merge-queue
+  - /managing-suggestions-to-update-pull-request-branches
   - /managing-auto-merge-for-pull-requests-in-your-repository
   - /managing-the-automatic-deletion-of-branches
 shortTitle: Configure merges de PR
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 0e220bf3e8..3551fb459b 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -26,4 +26,4 @@ Se você permitir uma merge automático para pull requests no seu repositório,
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Em "Botão de merge", selecione ou desmarque a opção **Permitir merge automático**. ![Caixa de seleção para permitir ou impedir merge automático](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
+1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**. ![Caixa de seleção para permitir ou impedir merge automático](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
new file mode 100644
index 0000000000..a724a1302b
--- /dev/null
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -0,0 +1,23 @@
+---
+title: Managing suggestions to update pull request branches
+intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+versions:
+  fpt: '*'
+  ghes: '> 3.4'
+  ghae: issue-6069
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage branch updates
+permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
+---
+
+## About suggestions to update a pull request branch
+
+If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+## Managing suggestions to update a pull request branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**. ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
index c4785bb925..f7ad1625b1 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
@@ -19,7 +19,7 @@ Qualquer pessoa com permissões de administrador em um repositório pode habilit
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Abaixo do "Merge button" (Botão de merge) marque ou desmarque a opção **Automatically delete head branches** (Excluir automaticamente branches head). ![Caixa de seleção para habilitar ou desabilitar a exclusão automática de branches](/assets/images/help/repository/automatically-delete-branches.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or unselect **Automatically delete head branches**. ![Caixa de seleção para habilitar ou desabilitar a exclusão automática de branches](/assets/images/help/repository/automatically-delete-branches.png)
 
 ## Leia mais
 - "[Fazer merge de uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 794ec47de6..9b15e9b64d 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -52,7 +52,8 @@ Quando você transfere um repositório, também são transferidos problemas, pul
   $ git remote set-url origin <em>new_url</em>
   ```
 
-- Quando você transfere um repositório de uma organização para uma conta de usuário, os colaboradores somente leitura do repositório não serão transferidos. Isso acontece porque os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
+- Quando você transfere um repositório de uma organização para uma conta de usuário, os colaboradores somente leitura do repositório não serão transferidos. Isso acontece porque os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
+- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
 Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 356f260ada..b00a22be19 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -51,6 +51,8 @@ Para reduzir o tamanho do seu arquivo CODEOWNERS, considere o uso de padrões cu
 Um arquivo CODEOWNERS usa um padrão que segue a maioria das mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), com [algumas exceções](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Os usuários devem ter acessso de `leitura` ao repositório e as equipes devem ter acesso explícito de `gravação`, mesmo que os integrantes da equipe já tenham acesso. Você também pode se referir a um usuário por um endereço de e-mail que foi adicionado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, por exemplo `user@example.com`.
 
 Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões.
+
+CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 ### Exemplo de um arquivo CODEOWNERS
 ```
 # Este é um comentário.
@@ -98,6 +100,10 @@ apps/ @octocat
 # subdirectories.
 /docs/ @doctocat
 
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
 # In this example, @octocat owns any file in the `/apps` 
 # directory in the root of your repository except for the `/apps/github` 
 # subdirectory, as its owners are left empty.
@@ -113,21 +119,6 @@ Existem algumas regras de sintaxe para arquivos gitignore que não funcionam em
 ## Proteção de branch e de CODEOWNERS
 Os proprietários do repositório podem adicionar regras de proteção de branch para garantir que o código alterado seja revisado pelos proprietários dos arquivos alterados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
 
-### Exemplo de um arquivo CODEOWNERS
-```
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat.
-/apps/ @doctocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat or @octocat.
-/apps/ @doctocat @octocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from a member of the @example-org/content team.
-/apps/ @example-org/content-team
-```
-
 
 ## Leia mais
 
diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md
index 3ebfc87076..0be3dd1a44 100644
--- a/translations/pt-BR/content/rest/guides/delivering-deployments.md
+++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md
@@ -20,7 +20,7 @@ A [API de Implantações][deploy API] fornece seus projetos hospedados em {% dat
 
 Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos:
 
-* Fazer merge de um pull request
+* Merge a pull request.
 * Quando a CI terminar, definiremos o status do pull request.
 * Quando o pull request for mesclado, executaremos a nossa implantação no nosso servidor.
 
diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
index d0071d136b..7fbf8bf758 100644
--- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
@@ -42,9 +42,9 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > Content-Type: application/json; charset=utf-8
 > ETag: "a00049ba79152d03380c34652f2cb612"
 > X-GitHub-Media-Type: github.v3
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4987
-> X-RateLimit-Reset: 1350085394{% ifversion ghes %}
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4987
+> x-ratelimit-reset: 1350085394{% ifversion ghes %}
 > X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %}
 > X-GitHub-Enterprise-Version: GitHub AE{% endif %}
 > Content-Length: 5
@@ -372,16 +372,16 @@ Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu st
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 56
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 56
+> x-ratelimit-reset: 1372700873
 ```
 
 | Nome do Cabeçalho       | Descrição                                                                                                                                         |
 | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `X-RateLimit-Limit`     | O número máximo de solicitações que você pode fazer por hora.                                                                                     |
-| `X-RateLimit-Remaining` | O número de solicitações restantes na janela de limite de taxa atual.                                                                             |
-| `X-RateLimit-Reset`     | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). |
+| `x-ratelimit-limit`     | O número máximo de solicitações que você pode fazer por hora.                                                                                     |
+| `x-ratelimit-remaining` | O número de solicitações restantes na janela de limite de taxa atual.                                                                             |
+| `x-ratelimit-reset`     | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). |
 
 Se você precisar de outro formato de tempo, qualquer linguagem de programação moderna pode fazer o trabalho. Por exemplo, se você abrir o console em seu navegador, você pode facilmente obter o tempo de redefinição como um objeto de tempo do JavaScript.
 
@@ -395,9 +395,9 @@ Se você exceder o limite de taxa, uma resposta do erro retorna:
 ```shell
 > HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 0
-> X-RateLimit-Reset: 1377013266
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 0
+> x-ratelimit-reset: 1377013266
 
 > {
 >    "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
@@ -413,9 +413,9 @@ If your OAuth App needs to make unauthenticated calls with a higher rate limit,
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4966
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4966
+> x-ratelimit-reset: 1372700873
 ```
 
 {% note %}
@@ -495,9 +495,9 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
 > HTTP/2 304
@@ -505,18 +505,18 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
 > HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 ```
 
 ## Compartilhamento de recursos de origem cruzada
@@ -529,7 +529,7 @@ Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `htt
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
 HTTP/2 302
 Access-Control-Allow-Origin: *
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
 
 A solicitação pré-voo de CORS se parece com isso:
@@ -540,7 +540,7 @@ HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 Access-Control-Max-Age: 86400
 ```
 
@@ -554,9 +554,9 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > /**/foo({
 >   "meta": {
 >     "status": 200,
->     "X-RateLimit-Limit": "5000",
->     "X-RateLimit-Remaining": "4966",
->     "X-RateLimit-Reset": "1372700873",
+>     "x-ratelimit-limit": "5000",
+>     "x-ratelimit-remaining": "4966",
+>     "x-ratelimit-reset": "1372700873",
 >     "Link": [ // pagination headers and other links
 >       ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}]
 >     ]
@@ -658,3 +658,4 @@ Se as etapas acima não resultarem em nenhuma informação, usaremos UTC como o
 [uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
+
diff --git a/translations/pt-BR/content/rest/reference/scim.md b/translations/pt-BR/content/rest/reference/scim.md
index cc34a0cb4f..3f7196be82 100644
--- a/translations/pt-BR/content/rest/reference/scim.md
+++ b/translations/pt-BR/content/rest/reference/scim.md
@@ -33,15 +33,15 @@ Você deve efetuar a autenticação como dono de uma organização do {% data va
 
 ### Atributos de usuário de SCIM compatíveis
 
-| Nome             | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ---------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `userName`       | `string`  | O nome de usuário para o usuário.                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `name.givenName` | `string`  | O primeiro nome do usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `name.lastName`  | `string`  | O sobrenome do usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `emails`         | `array`   | Lista de e-mails dos usuários.                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `externalId`     | `string`  | Este identificador é gerado pelo provedor do SAML e é usado como um ID exclusivo pelo provedor do SAML para corresponder ao usuário do GitHub. Você pode encontrar o `externalID` para um usuário no provedor do SAML ou usar a [listar identidades fornecidas pelo ponto de extremidade do SCIM](#list-scim-provisioned-identities) e filtrar outros atributos conhecidos, como, por exemplo, o nome de usuário no GitHub ou endereço de e-mail de usuário. |
-| `id`             | `string`  | Identificador gerado pelo ponto de extremidade do SCIM do GitHub.                                                                                                                                                                                                                                                                                                                                                                                            |
-| `ativo`          | `boolean` | Usado para indicar se a identidade está ativa (verdadeira) ou se deve ser desprovisionada (falso).                                                                                                                                                                                                                                                                                                                                                           |
+| Nome              | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ----------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `userName`        | `string`  | O nome de usuário para o usuário.                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `name.givenName`  | `string`  | O primeiro nome do usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `name.familyName` | `string`  | O sobrenome do usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `emails`          | `array`   | Lista de e-mails dos usuários.                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `externalId`      | `string`  | Este identificador é gerado pelo provedor do SAML e é usado como um ID exclusivo pelo provedor do SAML para corresponder ao usuário do GitHub. Você pode encontrar o `externalID` para um usuário no provedor do SAML ou usar a [listar identidades fornecidas pelo ponto de extremidade do SCIM](#list-scim-provisioned-identities) e filtrar outros atributos conhecidos, como, por exemplo, o nome de usuário no GitHub ou endereço de e-mail de usuário. |
+| `id`              | `string`  | Identificador gerado pelo ponto de extremidade do SCIM do GitHub.                                                                                                                                                                                                                                                                                                                                                                                            |
+| `ativo`           | `boolean` | Usado para indicar se a identidade está ativa (verdadeira) ou se deve ser desprovisionada (falso).                                                                                                                                                                                                                                                                                                                                                           |
 
 {% note %}
 
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
index 8fe65e37b6..8c615f1523 100644
--- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -49,6 +49,43 @@ shortTitle: Gerenciar camadas de pagamento
 {% data reusables.sponsors.tier-update %}
 {% data reusables.sponsors.retire-tier %}
 
+## Adding a repository to a sponsorship tier
+
+{% data reusables.sponsors.sponsors-only-repos %}
+
+### About adding repositories to a sponsorship tier
+
+To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository.
+
+When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled.
+
+Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier.
+
+You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync.
+
+### About transfers for repositories that are added to sponsorship tiers
+
+If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected.
+
+- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors.
+- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository.
+- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository.
+
+### Adding a repository a sponsorship tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+1. Select **Grant sponsors access to a private repository**.
+
+   ![Screenshot of checkbox to grant sponsors access to a private repository](/assets/images/help/sponsors/grant-sponsors-access-to-repo-checkbox.png)
+
+1. Select the dropdown menu and click the repository you want to add.
+
+   ![Screenshot of dropdown menu to choose the repository to grant sponsors access to](/assets/images/help/sponsors/grant-sponsors-access-to-repo-dropdown.png)
+
+{% data reusables.sponsors.tier-update %}
+
 ## Habilitar camadas com quantidades personalizadas
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
diff --git a/translations/pt-BR/data/features/code-scanning-task-lists.yml b/translations/pt-BR/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..0de30490f7
--- /dev/null
+++ b/translations/pt-BR/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/translations/pt-BR/data/features/codeql-ml-queries.yml b/translations/pt-BR/data/features/codeql-ml-queries.yml
new file mode 100644
index 0000000000..c74f86b77f
--- /dev/null
+++ b/translations/pt-BR/data/features/codeql-ml-queries.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5604.
+#Documentation for the beta release of CodeQL queries boosted by machine learning
+#to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/pt-BR/data/product-examples/README.md b/translations/pt-BR/data/product-examples/README.md
index 697b726d9c..984c1ff048 100644
--- a/translations/pt-BR/data/product-examples/README.md
+++ b/translations/pt-BR/data/product-examples/README.md
@@ -2,7 +2,7 @@
 
 As páginas que usam o layout de `product-landing` podem, opcionalmente, incluir uma seção de `exemplos`. Atualmente, apoiamos três tipos de exemplos:
 
-1. Exemplos de código Consulte https://docs.github.com/en/actions#code-examples.
+1. Exemplos de código Consulte https://docs.github.com/en/codespaces#code-examples.
 
 2. Exemplos da comunidade Consulte https://docs.github.com/en/discussions#community-examples.
 
@@ -10,7 +10,7 @@ As páginas que usam o layout de `product-landing` podem, opcionalmente, incluir
 
 ## Como funciona
 
-Os dados de exemplo para cada produto são definidos em `data/product-landing-examples`, em um subdiretório denominado para o produto **** e um arquivo YML denominado para o tipo de **** (p. ex., `data/product-examples/sponsors/user-examples.yml` ou `data/product-examples/actions/code-examples.yml`). Atualmente, temos compatibilidade com apenas um tipo de exemplo por produto.
+Example data for each product is defined in `data/product-landing-examples`, in a subdirectory named for the **product** and a YML file named for the **example type** (e.g., `data/product-examples/sponsors/user-examples.yml` or `data/product-examples/codespaces/code-examples.yml`). Atualmente, temos compatibilidade com apenas um tipo de exemplo por produto.
 
 ### Controle de Versão
 
diff --git a/translations/pt-BR/data/product-examples/actions/code-examples.yml b/translations/pt-BR/data/product-examples/actions/code-examples.yml
deleted file mode 100644
index 584d3aeb02..0000000000
--- a/translations/pt-BR/data/product-examples/actions/code-examples.yml
+++ /dev/null
@@ -1,335 +0,0 @@
----
-- 
-  title: Serviços de exemplo
-  description: Exemplos de fluxos de trabalho que usam contêineres do serviço
-  languages: JavaScript
-  href: actions/example-services
-  tags:
-    - contêineres de serviço
-- 
-  title: Configurar as etiquetas do GitHub de forma declarativa
-  description: Ação do GitHub para configurar as etiquetas em repositórios de forma declarativa
-  languages: JavaScript
-  href: lannonbr/issue-label-manager-action
-  tags:
-    - Problemas
-    - etiquetas
-- 
-  title: Sincronizar as etiquetas do GitHub de forma declarativa
-  description: Ação do GitHub para sincronizar as etiquetas do GitHub de forma declarativa
-  languages: 'Go, Dockerfile'
-  href: micnncim/action-label-syncer
-  tags:
-    - Problemas
-    - etiquetas
-- 
-  title: Adicionar versões ao GitHub
-  description: Publicar versões do GitHub em uma ação
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Github-Release-Action
-  tags:
-    - releases
-    - publicar
-- 
-  title: Publicar uma imagem do docker no Dockerhub
-  description: Uma ação do GitHub usada para construir e publicar imagens Docker
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Publish-Docker-Github-Action
-  tags:
-    - docker
-    - publicar
-    - build
-- 
-  title: Criar um problema usando o conteúdo de um arquivo
-  description: Uma ação do GitHub para criar um problema que usa conteúdo de um arquivo
-  languages: 'JavaScript, Python'
-  href: peter-evans/create-issue-from-file
-  tags:
-    - Problemas
-- 
-  title: Publicar versões do GitHub com Ativos
-  description: GitHub Action para criar versões do GitHub
-  languages: 'TypeScript, Shell, JavaScript'
-  href: softprops/action-gh-release
-  tags:
-    - releases
-    - publicar
-- 
-  title: GitHub Project Automation+
-  description: Automatizar cartões de projeto do GitHub com qualquer evento de webhook
-  languages: JavaScript
-  href: alex-page/github-project-automation-plus
-  tags:
-    - projetos
-    - automação
-    - Problemas
-    - Pull requests
-- 
-  title: Executar o GitHub Actions localmente com uma interface web
-  description: Executa localmente os fluxos de trabalho do GitHub Actions (local)
-  languages: 'JavaScript, HTML, Dockerfile, CSS'
-  href: phishy/wflow
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: Execute localmente o seu GitHub Actions
-  description: Execute o GitHub Actions localmente no Terminal
-  languages: 'Go, Shell'
-  href: nektos/act
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: Cria e publica uma APK de depuração no Android
-  description: Cria e lança a APK de depuração do seu projeto de Android
-  languages: 'Shell, Dockerfile'
-  href: ShaunLWM/action-release-debugapk
-  tags:
-    - android
-    - build
-- 
-  title: Gerar números sequenciais de criação para o GitHub Actions
-  description: GitHub Action para gerar números de criação sequenciais.
-  languages: JavaScript
-  href: einaregilsson/build-number
-  tags:
-    - build
-    - automação
-- 
-  title: Ações do GitHub para fazer push novamente para o repositório
-  description: Fazer envio por push das alterações do Git para o repositório do GitHub sem dificuldade de autenticação
-  languages: 'JavaScript, Shell'
-  href: ad-m/github-push-action
-  tags:
-    - publicar
-- 
-  title: Gerar observações de versão com base nos seus eventos
-  description: Ação para gerar automaticamente uma observação de versão com base nos seus eventos
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/release-notes-generator-action
-  tags:
-    - releases
-    - publicar
-- 
-  title: Criar uma página wiki do GitHub com base no arquivo de markdown fornecido
-  description: Criar uma página wiki do GitHub com base no arquivo de markdown fornecido
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/wiki-page-creator-action
-  tags:
-    - wiki
-    - publicar
-- 
-  title: Etiqueta os seus pull requests automaticamente (usando arquivos de commit)
-  description: Ação do GitHub para etiquetar automaticamente seus pull requests (usando arquivos de commit)
-  languages: 'TypeScript, Dockerfile, JavaScript'
-  href: Decathlon/pull-request-labeler-action
-  tags:
-    - projetos
-    - Problemas
-    - etiquetas
-- 
-  title: Adicionar etiqueta aos seus Pull Requests com base no nome da equipe do autor
-  description: Ação do GitHub para etiquetar os seus pull requests com base no nome do autor
-  languages: 'TypeScript, JavaScript'
-  href: JulienKode/team-labeler-action
-  tags:
-    - pull request
-    - etiquetas
-- 
-  title: Obtém uma lista de alterações de arquivo por PR/Push
-  description: Essa ação irá conferir a você saídas dos arquivos que mudaram no seu repositório
-  languages: 'TypeScript, Shell, JavaScript'
-  href: trilom/file-changes-action
-  tags:
-    - fluxo de trabalho
-    - repositório
-- 
-  title: Ações privadas em qualquer fluxo de trabalho
-  description: Permite que o GitHub Actions seja facilmente reutilizado
-  languages: 'TypeScript, JavaScript, Shell'
-  href: InVisionApp/private-action-loader
-  tags:
-    - fluxo de trabalho
-    - tools
-- 
-  title: Etiqueta os seus problemas usando o conteúdo do problema
-  description: Um GitHub Action para marcar automaticamente problemas com etiquetas e responsáveis
-  languages: 'JavaScript, TypeScript'
-  href: damccorm/tag-ur-it
-  tags:
-    - fluxo de trabalho
-    - tools
-    - etiquetas
-    - Problemas
-- 
-  title: Reverter uma versão do GitHub
-  description: Um GitHub Action para reverter ou excluir uma versão
-  languages: 'JavaScript'
-  href: author/action-rollback
-  tags:
-    - fluxo de trabalho
-    - releases
-- 
-  title: Bloquear problemas e pull requests fechados
-  description: GitHub Action que bloqueia problemas e pull requests fechados após um período de inatividade
-  languages: 'JavaScript'
-  href: dessant/lock-threads
-  tags:
-    - Problemas
-    - Pull requests
-    - fluxo de trabalho
-- 
-  title: Obter a contagem de diferença de commit entre dois branches
-  description: Este GitHub Action compara dois branches e fornece a você a contagem do commit entre eles
-  languages: 'JavaScript, Shell'
-  href: jessicalostinspace/commit-difference-action
-  tags:
-    - commit
-    - diff
-    - fluxo de trabalho
-- 
-  title: Gerar notas de versão com base em referências do Git
-  description: GitHub Action para gerar registros de alterações e observações de versão
-  languages: 'JavaScript, Shell'
-  href: metcalfc/changelog-generator
-  tags:
-    - cicd
-    - release-notes
-    - fluxo de trabalho
-    - registro de alterações
-- 
-  title: Aplica Políticas nos Repositórios e Commits do GitHub
-  description: Requisitos de política para os seus pipelines
-  languages: 'Go, Makefile, Dockerfile, Shell'
-  href: talos-systems/conform
-  tags:
-    - docker
-    - build-automation
-    - fluxo de trabalho
-- 
-  title: Etiqueta automática com base em problemas
-  description: Etiquetar automaticamente um problema com base na descrição do mesmo
-  languages: 'TypeScript, JavaScript, Dockerfile'
-  href: Renato66/auto-label
-  tags:
-    - etiquetas
-    - fluxo de trabalho
-    - automação
-- 
-  title: Atualiza as GitHub Actions configuradas para as últimas versões
-  description: Ferramenta de CLI para verificar se todas as suas ações estão atualizadas ou não
-  languages: 'C#, Inno Setup, PowerShell, Shell'
-  href: fabasoad/ghacu
-  tags:
-    - versions
-    - cli
-    - fluxo de trabalho
-- 
-  title: Criar um branch de problema
-  description: O GitHub Action que automatiza a criação de branches de problemas
-  languages: 'JavaScript, Shell'
-  href: robvanderleek/create-issue-branch
-  tags:
-    - probot
-    - Problemas
-    - etiquetas
-- 
-  title: Remover artefatos antigos
-  description: Personaliza limpeza de artefato
-  languages: 'JavaScript, Shell'
-  href: c-hive/gha-remove-artifacts
-  tags:
-    - artefatos
-    - fluxo de trabalho
-- 
-  title: Sincronizar Arquivos/Binários definidos para um Wiki ou para Repositórios Externos
-  description: GitHub Action para sincronizar automaticamente as alterações em repositórios externos como, por exemplo, o wiki
-  languages: 'Shell, Dockerfile'
-  href: kai-tub/external-repo-sync-action
-  tags:
-    - wiki
-    - sync
-    - fluxo de trabalho
-- 
-  title: Criar/Atualizar/Excluir uma página do Wiki do GitHub com base em qualquer arquivo
-  description: Atualiza a sua wiki do GitHub que usa rsync, permitindo exclusão de arquivos e diretórios, bem como a exclusão real de arquivos
-  languages: 'Shell, Dockerfile'
-  href: Andrew-Chen-Wang/github-wiki-action
-  tags:
-    - wiki
-    - docker
-    - fluxo de trabalho
-- 
-  title: GitHub Actions de Prow
-  description: Automação da aplicação das políticas, chat-ops e fusão automática de PR
-  languages: 'TypeScript, JavaScript'
-  href: jpmcb/prow-github-actions
-  tags:
-    - chat-ops
-    - prow
-    - fluxo de trabalho
-- 
-  title: Verifica o status do GitHub no seu fluxo de trabalho
-  description: Verifica o Status do GitHub no seu fluxo de trabalho
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-status
-  tags:
-    - status
-    - monitoramento
-    - fluxo de trabalho
-- 
-  title: Gerencia etiquetas no GitHub como código
-  description: GitHub Action para gerenciar etiquetas (criar/renomear/atualizar/excluir)
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-labeler
-  tags:
-    - etiquetas
-    - fluxo de trabalho
-    - automação
-- 
-  title: Distribuir financiamento em projetos grátis e de código aberto
-  description: Distribuição contínua de financiamento para os colaboradores e dependências do projeto
-  languages: 'Python, Dockerfile, Shell, Ruby'
-  href: protontypes/libreselery
-  tags:
-    - sponsors
-    - financiamento
-    - payment
-- 
-  title: Regras do Herald para o GitHub
-  description: Adicionar revisores, assinantes, etiquetas e responsáveis ao seu PR
-  languages: 'TypeScript, JavaScript'
-  href: gagoar/use-herald-action
-  tags:
-    - reviewers
-    - etiquetas
-    - assignees
-    - pull request
-- 
-  title: Validador de Codeowner
-  description: Garante a exatidão do seu arquivo de CODEOWNERS do GitHub, suporta os repositórios do GitHub público e privado, bem como as instalações do GitHub Enterprise
-  languages: 'Go, Shell, Makefile, Dockerfile'
-  href: mszostok/codeowners-validator
-  tags:
-    - codeowners
-    - validar
-    - fluxo de trabalho
-- 
-  title: Ação Copybara
-  description: Move e transforma o código entre repositórios (ideal para manter vários repositórios de um monorrepositório)
-  languages: 'TypeScript, JavaScript, Shell'
-  href: olivr/copybara-action
-  tags:
-    - monorepo
-    - copybara
-    - fluxo de trabalho
-- 
-  title: Implanta arquivos estáticos no GitHub Pages
-  description: GitHub Action para publicar o site no GitHub Pages automaticamente
-  languages: 'TypeScript, JavaScript'
-  href: peaceiris/actions-gh-pages
-  tags:
-    - publicar
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/24.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/24.yml
new file mode 100644
index 0000000000..ce227b3787
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/24.yml
@@ -0,0 +1,21 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador.
+    - As regras de firewall personalizadas são removidas durante o processo de atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.
+    - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/16.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/16.yml
new file mode 100644
index 0000000000..1e172d6872
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/16.yml
@@ -0,0 +1,25 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - Several documentation links resulted in a 404 Not Found error.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes.
+    - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador.
+    - As regras de firewall personalizadas são removidas durante o processo de atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - Se o {% data variables.product.prodname_actions %} estiver habilitado para {% data variables.product.prodname_ghe_server %}, a desmontagem de um nó de réplica com `ghe-repl-teardown` será bem-sucedida, mas poderá retornar `ERROR:Running migrations`.
+    - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/8.yml
new file mode 100644
index 0000000000..13e809f96e
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/8.yml
@@ -0,0 +1,26 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador.
+    - As regras de firewall personalizadas são removidas durante o processo de atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes.
+    - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/3.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/3.yml
new file mode 100644
index 0000000000..1ca31d2598
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/3.yml
@@ -0,0 +1,29 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - '**MEDIUM**:  Secret Scanning API calls could return alerts for repositories outside the scope of the request.'
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - As regras de firewall personalizadas são removidas durante o processo de atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes.
+    - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
diff --git a/translations/pt-BR/data/reusables/actions/oidc-permissions-token.md b/translations/pt-BR/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..cc6685b266
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,13 @@
+The job or workflow run requires a `permissions` setting with [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). This allows the JWT to be requested from GitHub's OIDC provider using one of these approaches:
+
+- Using environment variables on the runner (`ACTIONS_ID_TOKEN_REQUEST_URL` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Using `getIDToken()` from the Actions toolkit.
+
+If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
+
+```yaml{:copy}
+permissions:
+  id-token: write
+```
+
+Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho. 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/translations/pt-BR/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
index 7db5b9879a..6664cbfafc 100644
--- a/translations/pt-BR/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
+++ b/translations/pt-BR/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 
 {% note %}
 
diff --git a/translations/pt-BR/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/pt-BR/data/reusables/code-scanning/beta-codeql-ml-queries.md
new file mode 100644
index 0000000000..133b760b30
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -0,0 +1,9 @@
+{% if codeql-ml-queries %}
+
+{% note %}
+
+**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites-explanation.md
new file mode 100644
index 0000000000..48d2119256
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -0,0 +1,5 @@
+Os conjuntos de consulta a seguir foram criados em {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} e estão disponíveis para uso.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% if codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites.md b/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites.md
index 808bd21d73..12105bdd43 100644
--- a/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites.md
+++ b/translations/pt-BR/data/reusables/code-scanning/codeql-query-suites.md
@@ -1,8 +1,4 @@
-Os conjuntos de consulta a seguir foram criados em {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} e estão disponíveis para uso.
-
   | Suite de consulta      | Descrição                                                                       |
   |:---------------------- |:------------------------------------------------------------------------------- |
   | `security-extended`    | Consultas de menor gravidade e precisão que as consultas-padrão                 |
   | `security-and-quality` | Consultas de `security-extended`, mais consultas de manutenção e confiabilidade |
-
-Ao especificar um conjunto de pesquisas, o mecanismo de análise de {% data variables.product.prodname_codeql %} executará as consultas contidas no conjunto para você além do conjunto-padrão de consultas.
diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-billing.md b/translations/pt-BR/data/reusables/codespaces/codespaces-billing.md
index 5f57ec95f9..11850c800a 100644
--- a/translations/pt-BR/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/pt-BR/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
 {% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage.
 
 ### Calculating compute usage
-The total number of uptime minutes for which the {% data variables.product.prodname_codespaces %} instances are active. Compute usage is calculated by the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
+Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
 
-Uptime is controlled by stopping your codespace which can be done manually or based on period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
 
 ### Calculating storage usage
 For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. No final do mês, {% data variables.product.prodname_dotcom %} arredonda seu armazenamento para o MB mais próximo. 
diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/save-settings.md b/translations/pt-BR/data/reusables/enterprise_management_console/save-settings.md
index 0454795af9..a58fb67920 100644
--- a/translations/pt-BR/data/reusables/enterprise_management_console/save-settings.md
+++ b/translations/pt-BR/data/reusables/enterprise_management_console/save-settings.md
@@ -1,2 +1,2 @@
 1. Na barra lateral esquerda, clique **Save settings** (Salvar configurações). ![Botão Save settings (Salvar configurações) no {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-1. Aguarde a conclusão da execução de suas configurações.
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..a1cc2ae3c0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.product.product_location %}.
+
+{% endwarning %}
diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..6e8266d846
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,3 @@
+1. Aguarde a conclusão da execução de suas configurações.
+
+   ![Configurar a instância](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/translations/pt-BR/data/reusables/gated-features/user-repo-collaborators.md b/translations/pt-BR/data/reusables/gated-features/user-repo-collaborators.md
index 880916722b..319b8698fd 100644
--- a/translations/pt-BR/data/reusables/gated-features/user-repo-collaborators.md
+++ b/translations/pt-BR/data/reusables/gated-features/user-repo-collaborators.md
@@ -1 +1,4 @@
-Se estiver usando o {% data variables.product.prodname_free_user %}, você poderá adicionar colaboradores ilimitados em repositórios públicos e privados.
+{% ifversion fpt %}
+If you're using
+{% data variables.product.prodname_free_user %}, you can add unlimited collaborators on public and private repositories.
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/organizations/billing-settings.md b/translations/pt-BR/data/reusables/organizations/billing-settings.md
index 45d230b82a..feb35fd556 100644
--- a/translations/pt-BR/data/reusables/organizations/billing-settings.md
+++ b/translations/pt-BR/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
 {% data reusables.user_settings.access_settings %}
-2. In the settings sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% data reusables.profile.org_settings %}
-1. If you're an organization owner, in the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/pt-BR/data/reusables/organizations/oauth_app_access.md b/translations/pt-BR/data/reusables/organizations/oauth_app_access.md
index 79bbadb28b..a2dc8773f5 100644
--- a/translations/pt-BR/data/reusables/organizations/oauth_app_access.md
+++ b/translations/pt-BR/data/reusables/organizations/oauth_app_access.md
@@ -1,3 +1 @@
-{% ifversion fpt or ghec %}
-  1. Na barra lateral de configurações, clique em **Third-party access** (Acesso de terceiros). ![{% data variables.product.prodname_oauth_app %} acessar a aba na barra lateral esquerda](/assets/images/help/settings/settings-sidebar-third-party-access.png)
-{% endif %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
diff --git a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
index 1907f8b6d2..31946ac488 100644
--- a/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
+++ b/translations/pt-BR/data/reusables/organizations/teams_sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
 1. Na barra lateral de configurações, clique em **Teams** (Equipes). ![Aba de equipes na barra lateral de configurações da organização](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/profile/org_member_privileges.md b/translations/pt-BR/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..c0462ae849
--- /dev/null
+++ b/translations/pt-BR/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1 @@
+3. Under "Access", click **Member privileges**. ![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png) 
diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
index 761c86ed99..2e387d66c7 100644
--- a/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/pt-BR/data/reusables/repositories/sidebar-notifications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
 1. Clique em **Notificações**. ![Botão de notificações na barra lateral](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/security/compliance-report-list.md b/translations/pt-BR/data/reusables/security/compliance-report-list.md
new file mode 100644
index 0000000000..a8d6d1a87e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/security/compliance-report-list.md
@@ -0,0 +1,4 @@
+- SOC 1, Tipo 2
+- SOC 2, Tipo 2
+- Cloud Security Alliance CAIQ self-assessment (CSA CAIQ)
+- {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/security/compliance-report-screenshot.md b/translations/pt-BR/data/reusables/security/compliance-report-screenshot.md
new file mode 100644
index 0000000000..984c8d6d8b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/security/compliance-report-screenshot.md
@@ -0,0 +1 @@
+![Screenshot of download button to the right of a compliance report](/assets/images/help/settings/compliance-report-download.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/sponsors/sponsors-only-repos.md b/translations/pt-BR/data/reusables/sponsors/sponsors-only-repos.md
new file mode 100644
index 0000000000..0361572c97
--- /dev/null
+++ b/translations/pt-BR/data/reusables/sponsors/sponsors-only-repos.md
@@ -0,0 +1 @@
+You can give all sponsors in a tier access to a private repository by adding the repository to the tier.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/sponsors/tier-details.md b/translations/pt-BR/data/reusables/sponsors/tier-details.md
index dc63a59f4d..d535491ef1 100644
--- a/translations/pt-BR/data/reusables/sponsors/tier-details.md
+++ b/translations/pt-BR/data/reusables/sponsors/tier-details.md
@@ -3,10 +3,11 @@ You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for spon
 Você pode personalizar as recompensas para cada camada. Por exemplo, as recompensas para uma camada poderiam incluir:
 - Acesso antecipado a novas versões
 - Logotipo ou nome no LEIAME
-- Acesso ao repositório privado
 - Atualizações semanais do boletim informativo
 - Outras recompensas que seus patrocinadores gostariam ✨
 
+{% data reusables.sponsors.sponsors-only-repos %} For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)."
+
 You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email.
 
 Depois de publicar uma camada, você não pode editar o preço dessa camada. Em vez disso, você deve se retirar a camada e criar uma nova. Os patrocinadores existentes permanecerão na camada retirada até que mudem a sua camada de patrocínio, cancelem seu patrocínio ou seu período de patrocínio único vença.
diff --git a/translations/pt-BR/data/reusables/user-settings/oauth_apps.md b/translations/pt-BR/data/reusables/user-settings/oauth_apps.md
index 8129e43de1..92b9066bdd 100644
--- a/translations/pt-BR/data/reusables/user-settings/oauth_apps.md
+++ b/translations/pt-BR/data/reusables/user-settings/oauth_apps.md
@@ -1 +1 @@
-1. Na barra lateral esquerda, clique em **Aplicativos OAuth**. ![Seção de aplicativos OAuth](/assets/images/help/settings/developer-settings-oauth-apps.png)
+1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_oauth_apps %}**. ![Seção de aplicativos OAuth](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/access_applications.md b/translations/pt-BR/data/reusables/user_settings/access_applications.md
index bb76f4e95e..7db741ea14 100644
--- a/translations/pt-BR/data/reusables/user_settings/access_applications.md
+++ b/translations/pt-BR/data/reusables/user_settings/access_applications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Applications** (Aplicativos). ![Aba aplicativos](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/accessibility_settings.md b/translations/pt-BR/data/reusables/user_settings/accessibility_settings.md
index b23486a3ff..2c9e37e2f4 100644
--- a/translations/pt-BR/data/reusables/user_settings/accessibility_settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/accessibility_settings.md
@@ -1 +1 @@
-1. In the navigation on the left hand side, click the **Accessibility** link. ![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)
+1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**.
diff --git a/translations/pt-BR/data/reusables/user_settings/account_settings.md b/translations/pt-BR/data/reusables/user_settings/account_settings.md
index d38751140a..ced72b8186 100644
--- a/translations/pt-BR/data/reusables/user_settings/account_settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/account_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Conta**. ![Opção do menu configurações da conta](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/appearance-settings.md b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
index 8cdc9ed93d..050370bf13 100644
--- a/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
 1. Na barra lateral de configurações do usuário, clique em **Aparência**.
 
-   ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
+   ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/user_settings/billing_plans.md b/translations/pt-BR/data/reusables/user_settings/billing_plans.md
index 8d26ab1479..333102205b 100644
--- a/translations/pt-BR/data/reusables/user_settings/billing_plans.md
+++ b/translations/pt-BR/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/pt-BR/data/reusables/user_settings/blocked_users.md b/translations/pt-BR/data/reusables/user_settings/blocked_users.md
index 0e40b62403..b7ba502dca 100644
--- a/translations/pt-BR/data/reusables/user_settings/blocked_users.md
+++ b/translations/pt-BR/data/reusables/user_settings/blocked_users.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Blocked users** under **Moderation settings**. ![Aba de usuários bloqueados](/assets/images/help/settings/settings-sidebar-blocked-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**.
diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md b/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md
index 389c32f3e0..5aa532885e 100644
--- a/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md
+++ b/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md
@@ -1 +1 @@
-1. Na barra lateral esquerda, clique em **Codespaces**. ![Aba de codespaces na barra lateral de configurações do usuário](/assets/images/help/settings/codespaces-tab.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/pt-BR/data/reusables/user_settings/developer_settings.md b/translations/pt-BR/data/reusables/user_settings/developer_settings.md
index 5bf74d6232..a7c3a03398 100644
--- a/translations/pt-BR/data/reusables/user_settings/developer_settings.md
+++ b/translations/pt-BR/data/reusables/user_settings/developer_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Developer settings** (Configurações do desenvolvedor). ![Configurações do desenvolvedor](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/emails.md b/translations/pt-BR/data/reusables/user_settings/emails.md
index 4f34bf9d4d..ede0a651c5 100644
--- a/translations/pt-BR/data/reusables/user_settings/emails.md
+++ b/translations/pt-BR/data/reusables/user_settings/emails.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
 1. Na barra lateral esquerda, clique em **E-mails**. ![Aba de e-mails](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/organizations.md b/translations/pt-BR/data/reusables/user_settings/organizations.md
index 02c25b7217..2e922b6ced 100644
--- a/translations/pt-BR/data/reusables/user_settings/organizations.md
+++ b/translations/pt-BR/data/reusables/user_settings/organizations.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
 1. Na barra lateral de configurações do usuário, clique em **Organizações**. ![Configurações do usuário para organizações](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/repo-tab.md b/translations/pt-BR/data/reusables/user_settings/repo-tab.md
index 8d4cd6a0cb..bba693a256 100644
--- a/translations/pt-BR/data/reusables/user_settings/repo-tab.md
+++ b/translations/pt-BR/data/reusables/user_settings/repo-tab.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/saved_replies.md b/translations/pt-BR/data/reusables/user_settings/saved_replies.md
index 72b799bc46..4518824f63 100644
--- a/translations/pt-BR/data/reusables/user_settings/saved_replies.md
+++ b/translations/pt-BR/data/reusables/user_settings/saved_replies.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Respostas salvas**. ![Aba de respostas salvas](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/security-analysis.md b/translations/pt-BR/data/reusables/user_settings/security-analysis.md
index 80161d67b5..642735a0f6 100644
--- a/translations/pt-BR/data/reusables/user_settings/security-analysis.md
+++ b/translations/pt-BR/data/reusables/user_settings/security-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
 1. Na barra lateral esquerda, clique em **Security & analysis** (Segurança e análise). ![Configurações de segurança e análise](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/security.md b/translations/pt-BR/data/reusables/user_settings/security.md
index df053934c3..5fd1ae50cd 100644
--- a/translations/pt-BR/data/reusables/user_settings/security.md
+++ b/translations/pt-BR/data/reusables/user_settings/security.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
 1. Na barra lateral esquerda, clique em **segurança da conta**. ![Configurações de segurança da conta do usuário](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/user_settings/ssh.md b/translations/pt-BR/data/reusables/user_settings/ssh.md
index 52468bf730..2ba12f8b8c 100644
--- a/translations/pt-BR/data/reusables/user_settings/ssh.md
+++ b/translations/pt-BR/data/reusables/user_settings/ssh.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
 1. Na barra lateral de configurações do usuário, clique em **chaves SSH e GPG**. ![Chaves de autenticação](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index a85e34a0f2..5bbec24ecb 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -43,7 +43,7 @@ pages:
   article_version: 'Versão do artigo'
   miniToc: Neste artigo
   contributor_callout: This article is contributed and maintained by
-  all_enterprise_releases: All Enterprise releases
+  all_enterprise_releases: All Enterprise Server releases
 errors:
   oops: Ops!
   something_went_wrong: Parece que algo deu errado.
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
index e72bc71121..7c91d2706b 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
@@ -46,7 +46,7 @@ To follow-up on notifications, you might consider the question "What was I block
 
 例如，您可以决定按照以下顺序采取后续行动：
   - 分配给您的议题和拉取请求。 立即关闭您可以关闭的任何议题或拉取请求，并添加更新。 需要时，保存通知供以后查看。
-  - 查看已保存的收件箱中的通知，尤其是未读更新。 如果帖子不再相关，请取消选中 {% octicon "bookmark" aria-label="The bookmark icon" %} 以从保存的收件箱中删除通知并取消保存它。
+  - 查看已保存的收件箱中的通知，尤其是未读更新。 If the thread is no longer relevant, deselect {% octicon "bookmark" aria-label="The bookmark icon" %} to remove the notification from the saved inbox and unsave it.
 
 ## 管理低优先级通知
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
index 9084cb9a07..7afb8f3d39 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -28,7 +28,7 @@ For more information about how contributions are calculated, see "[Managing cont
 {% note %}
 
 **Notes:**
-- The connection between your accounts is governed by <a href="/articles/github-privacy-statement/" class="dotcom-only">GitHub's Privacy Statement</a> and users enabling the connection agree to the <a href="/articles/github-terms-of-service/" class="dotcom-only">GitHub's Terms of Service</a>.
+- The connection between your accounts is governed by [GitHub's Privacy Statement](/free-pro-team@latest/github/site-policy/github-privacy-statement/) and users enabling the connection agree to the [GitHub's Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service).
 
 - Before you can connect your {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner.
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index 468ec12bb4..c9f2898800 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
-product: '{% ifversion fpt %}{% data reusables.gated-features.user-repo-collaborators %}{% endif %}'
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -38,8 +38,8 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
 1. 您邀请成为协作者的人员需提供用户名。{% ifversion fpt or ghec %} 如果他们还没有用户名，他们可以注册 {% data variables.product.prodname_dotcom %} 更多信息请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658%}
+{% data reusables.repositories.click-collaborators-teams %}
 1. 单击 **Invite a collaborator（邀请协作者）**。 !["邀请协作者" 按钮](/assets/images/help/repository/invite-a-collaborator-button.png)
 2. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field-user.png)
 3. 单击 **Add NAME to REPOSITORY（添加姓名到仓库）**。 ![用于添加协作者的按钮](/assets/images/help/repository/add-collaborator-user-repo.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 37fe983ecb..3bd5abf224 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -30,8 +30,8 @@ shortTitle: 删除协作者
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. 在要要删除的协作者的右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![用于删除协作者的按钮](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. 在左侧边栏中，单击 **Collaborators & teams（协作者和团队）**。 ![协作者选项卡](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index df3436b82c..564c5f2715 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -9,7 +9,6 @@ redirect_from:
   - /articles/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
-product: '{% data reusables.gated-features.user-repo-collaborators %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -22,6 +21,10 @@ shortTitle: 删除自己
 ---
 
 {% data reusables.user_settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 2. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
 3. 在您要离开的仓库旁边，单击 **Leave（离开）**。 ![离开按钮](/assets/images/help/repository/repo-leave.png)
 4. 仔细阅读警告，然后单击“I understand, leave this repository（我已了解，离开此仓库）”。 ![警告您离开的对话框](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
index 9fdbe9cdca..101067be19 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -13,12 +13,12 @@ shortTitle: 将 Jira 与项目集成
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
-3. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_apps %}**。 ![左侧边栏中的 {% data variables.product.prodname_oauth_apps %} 选项卡](/assets/images/help/settings/developer-settings-oauth-apps.png)
-3. 单击 **Register a new application（注册新应用程序）**。
-4. 在 **Application name（应用程序名称）**下输入 "Jira"。
-5. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。
-6. 在 **Authorization callback URL（授权回叫 URL）**下，输入 Jira 实例的完整 URL。
-7. 单击 **Register application（注册应用程序）**。 ![注册应用程序按钮](/assets/images/help/oauth/register-application-button.png)
+{% data reusables.user-settings.oauth_apps %}
+1. 单击 **Register a new application（注册新应用程序）**。
+2. 在 **Application name（应用程序名称）**下输入 "Jira"。
+3. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。
+4. 在 **Authorization callback URL（授权回叫 URL）**下，输入 Jira 实例的完整 URL。
+5. 单击 **Register application（注册应用程序）**。 ![注册应用程序按钮](/assets/images/help/oauth/register-application-button.png)
 8. 在 **Developer applications（开发者应用程序）**下，记下 "Client ID"（客户 ID）和 "Client Secret"（客户端密钥）值。 ![客户端 ID 和客户端密码](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 6ed1703cd1..e448e15fc4 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -14,5 +14,5 @@ shortTitle: Managing your tab size
 If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings.
 
 {% data reusables.user_settings.access_settings %}
-1. 在用户设置侧边栏中，单击 **Appearance（外观）**。 ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png)
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
 2. Under "Tab size preference", select the drop-down menu and choose your preference. ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
index 7df6bbf045..758ca92285 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
@@ -26,8 +26,7 @@ shortTitle: 管理预定提醒
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. 在要预定提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. 在要预定提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.days-dropdown %}
@@ -41,16 +40,14 @@ shortTitle: 管理预定提醒
 ## 管理用户帐户的预定提醒
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. 在要编辑预定提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. 在要编辑预定提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
 
 ## 删除用户帐户的预定提醒
 {% data reusables.user_settings.access_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/profile/scheduled-reminders-profile.png)
-3. 在要删除提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
+1. 在要删除提醒的组织旁边，单击 **Edit（编辑）**。 ![预定提醒编辑按钮](/assets/images/help/settings/scheduled-reminders-org-choice.png)
 {% data reusables.reminders.delete %}
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index d20a7e67f1..a51de191f0 100644
--- a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -88,7 +88,7 @@ If you are caching the package managers listed below, consider using the respect
 ### `cache` 操作的输入参数
 
 - `key`：**必要** 保存缓存时创建的键，以及用于搜索缓存的键。 可以是变量、上下文值、静态字符串和函数的任何组合。 密钥最大长度为 512 个字符，密钥长度超过最大长度将导致操作失败。
-- `path`：**必要** 运行器上缓存或还原的文件路径。 路径可以是绝对路径或相对于工作目录的路径。
+- `path`：**必要** 运行器上缓存或还原的文件路径。 The path can be an absolute path or relative to the workspace directory.
   - 路径可以是目录或单个文件，并且支持 glob 模式。
   - 使用 `cache` 操作的 `v2`，可以指定单个路径，也可以在单独的行上添加多个路径。 例如：
     ```
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index e677d40373..95692d2eeb 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -238,7 +238,7 @@ jobs:
 
 ## 嵌入代码
 
-下面的示例安装 `rubocop` 并用它来嵌入所有文件。 更多信息请参阅 [Rubocop](https://github.com/rubocop-hq/rubocop)。 您可以[配置 Rubocop](https://docs.rubocop.org/rubocop/configuration.html) 来决定特定的嵌入规则。
+下面的示例安装 `rubocop` 并用它来嵌入所有文件。 For more information, see [RuboCop](https://github.com/rubocop-hq/rubocop). 您可以[配置 Rubocop](https://docs.rubocop.org/rubocop/configuration.html) 来决定特定的嵌入规则。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
index a321ce6c56..256bb3fe41 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
@@ -84,7 +84,9 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
         - id: random-number-generator
           run: echo "::set-output name=random-id::$(echo $RANDOM)"
           shell: bash
-        - run: ${{ github.action_path }}/goodbye.sh
+        - run: echo "${{ github.action_path }}" >> $GITHUB_PATH
+          shell: bash          
+        - run: goodbye.sh
           shell: bash
     ```
     {% endraw %}
diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 7241c9833a..6d78d67c1b 100644
--- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -47,6 +47,8 @@ Docker 操作必须由默认 Docker 用户 (root) 运行。 不要在 `Dockerfil
 
 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。 有关 _exec_ 和 _shell_ 形式的更多信息，请参阅 Docker 文档中的 [ENTRYPOINT 参考](https://docs.docker.com/engine/reference/builder/#entrypoint)。
 
+You should not use `WORKDIR` to specify your entrypoint in your Dockerfile. Instead, you should use an absolute path. For more information, see [WORKDIR](#workdir).
+
 如果您配置容器使用 _exec_ 形式的 `ENTRYPOINT` 指令，在操作元数据文件中配置的 `args` 不会在命令 shell 中运行。 如果操作的 `args` 包含环境变量，不会替换该变量。 例如，使用以下 _exec_ 格式将不会打印存储在 `$GITHUB_SHA` 中的值， 但会打印 `"$GITHUB_SHA"`。
 
 ```dockerfile
diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 87bc65763f..24c80f1a28 100644
--- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -13,6 +13,7 @@ versions:
   ghae: '*'
   ghec: '*'
 type: reference
+miniTocMaxHeadingLevel: 4
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -20,7 +21,7 @@ type: reference
 
 ## 关于 {% data variables.product.prodname_actions %} 的 YAML 语法
 
-Docker 和 JavaScript 操作需要元数据文件。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 元数据文件中的数据定义操作的输入、输出和主要进入点。
+All actions require a metadata file. 元数据文件名必须是 `action.yml` 或 `action.yaml`。 The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
 
 操作元数据文件使用 YAML 语法。 如果您是 YAML 的新用户，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。
 
@@ -40,7 +41,7 @@ Docker 和 JavaScript 操作需要元数据文件。 元数据文件名必须是
 
 **可选** 输入参数用于指定操作在运行时预期使用的数据。 {% data variables.product.prodname_dotcom %} 将输入参数存储为环境变量。 大写的输入 ID 在运行时转换为小写。 建议使用小写输入 ID。
 
-### 示例
+### Example: Specifying inputs
 
 此示例配置两个输入：numOctocats 和 octocatEyeColor。 numOctocats 输入不是必要的，默认值为 '1'。 octocatEyeColor 输入是必要的，没有默认值。 使用此操作的工作流程文件必须使用 `with` 关键词来设置 octocatEyeColor 的输入值。 有关 `with` 语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)”。
 
@@ -83,13 +84,13 @@ inputs:
 
 **可选** 如果使用输入参数，此 `string` 将记录为警告消息。 您可以使用此警告通知用户输入已被弃用，并提及任何其他替代方式。
 
-## `outputs`
+## `outputs` for Docker container and JavaScript actions
 
 **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。  例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。
 
 如果不在操作元数据文件中声明输出，您仍然可以设置输出并在工作流程中使用它们。 有关在操作中设置输出的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)”。
 
-### 示例
+### Example: Declaring outputs for Docker container and JavaScript actions
 
 ```yaml
 outputs:
@@ -107,17 +108,11 @@ outputs:
 
 ## 用于复合操作的 `outputs`
 
-**可选** `outputs` 使用与 `outputs.<output_id>` 及 `outputs.<output_id>.description` 相同的参数（请参阅“用于 {% data variables.product.prodname_actions %}</a> 的
+**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
 
-`outputs`”），但也包括 `value` 令牌。</p> 
-
-
-
-### 示例
+### Example: Declaring outputs for composite actions
 
 {% raw %}
-
-
 ```yaml
 outputs:
   random-number:
@@ -130,35 +125,23 @@ runs:
       run: echo "::set-output name=random-id::$(echo $RANDOM)"
       shell: bash
 ```
-
-
 {% endraw %}
 
-
-
 ### `outputs.<output_id>.value`
 
 **必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。
 
 有关如何使用上下文语法的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-
-
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
-
-
+**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
 
 ## 用于 JavaScript 操作的 `runs`
 
 **Required** Configures the path to the action's code and the runtime used to execute the code.
 
-
-
-### Example using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
-
-
+### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
@@ -166,32 +149,23 @@ runs:
   main: 'main.js'
 ```
 
-
-
-
 ### `runs.using`
 
-**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
+**Required** The runtime used to execute the code specified in [`main`](#runsmain).
 
 - Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 - Use `node16` for Node.js v16.{% endif %}
 
-
-
 ### `runs.main`
 
 **必要** 包含操作代码的文件。 The runtime specified in [`using`](#runsusing) executes this file.
 
+### `runs.pre`
 
-
-### `pre`
-
-**可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. `pre:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。
+**可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
 
 在此示例中，`pre:` 操作运行名为 `setup.js` 的脚本：
 
-
-
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -200,10 +174,7 @@ runs:
   post: 'cleanup.js'
 ```
 
-
-
-
-### `pre-if`
+### `runs.pre-if`
 
 **可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
 
@@ -211,24 +182,17 @@ runs:
 
 在此示例中，`cleanup.js` 仅在基于 Linux 的运行器上运行：
 
-
-
 ```yaml
   pre: 'cleanup.js'
   pre-if: runner.os == 'linux'
 ```
 
-
-
-
-### `post`
+### `runs.post`
 
 **可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
 在此示例中，`post:` 操作会运行名为 `cleanup.js` 的脚本：
 
-
-
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -236,70 +200,44 @@ runs:
   post: 'cleanup.js'
 ```
 
-
 `post:` 操作始终默认运行，但您可以使用 `post-if` 覆盖该设置。
 
-
-
-### `post-if`
+### `runs.post-if`
 
 **可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 In `post-if`, status check functions evaluate against the job's status, not the action's own status.
 
 例如，此 `cleanup.js` 仅在基于 Linux 的运行器上运行：
 
-
-
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
-
-
-
 ## 用于复合操作的 `runs`
 
 **Required** Configures the path to the composite action.
 
-
-
 ### `runs.using`
 
 **Required** You must set this value to `'composite'`.
 
-
-
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-
-
-**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 
-
+**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。
 {% else %}
-
-**必要** 您计划在此操作中的步骤。 
-
+**必要** 您计划在此操作中的步骤。
 {% endif %}
 
-
-
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-
-
-**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
-
+**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
 {% else %}
-
-**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
-
+**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
 {% endif %}
 
 {% raw %}
-
-
 ```yaml
 runs:
   using: "composite"
@@ -307,14 +245,10 @@ runs:
     - run: ${{ github.action_path }}/test/script.sh
       shell: bash
 ```
-
-
 {% endraw %}
 
 或者，您也可以使用 `$GITHUB_ACTION_PATH`：
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -323,26 +257,17 @@ runs:
       shell: bash
 ```
 
-
 更多信息请参阅“[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
 
-
-
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-
-
-**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
-
+**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
 {% else %}
-
-**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
-
+**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
 {% endif %}
 
-
-
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 #### `runs.steps[*].if`
 
 **Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。
@@ -351,9 +276,7 @@ runs:
 
 **示例：使用上下文**
 
-此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
-
-
+ 此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
 
  ```yaml
 steps:
@@ -361,13 +284,10 @@ steps:
     if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
 ```
 
-
 **示例：使用状态检查功能**
 
 The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
-
-
 ```yaml
 steps:
   - name: My first step
@@ -376,49 +296,36 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
     uses: actions/heroku@1.0.0
 ```
-
-
-
+{% endif %}
 
 #### `runs.steps[*].name`
 
 **可选** 复合步骤的名称。
 
-
-
 #### `runs.steps[*].id`
 
 **可选** 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-
-
 #### `runs.steps[*].env`
 
 **可选** 设置环境变量的 `map` 仅用于该步骤。 If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
 
-
-
 #### `runs.steps[*].working-directory`
 
 **可选**  指定命令在其中运行的工作目录。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-
-
 #### `runs.steps[*].uses`
 
 **可选**  选择作为作业步骤一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
 
 强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
-
 - 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
 - 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
 - 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
 
 有些操作要求必须通过 [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -441,15 +348,10 @@ runs:
     - uses: docker://alpine:3.8
 ```
 
-
-
-
 #### `runs.steps[*].with`
 
 **可选** 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。  输入参数被设置为环境变量。 该变量的前缀为 INPUT_，并转换为大写。
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -461,21 +363,13 @@ runs:
         middle_name: The
         last_name: Octocat  
 ```
-
-
 {% endif %}
 
+## `runs` for Docker container actions
 
+**Required** Configures the image used for the Docker container action.
 
-## 用于 Docker 操作的 `runs`
-
-**必要** 配置用于 Docker 操作的图像。
-
-
-
-### 在仓库中使用 Dockerfile 的示例
-
-
+### Example: Using a Dockerfile in your repository
 
 ```yaml
 runs:
@@ -483,12 +377,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-
-
-
-### 使用公共 Docker 注册表容器的示例
-
-
+### Example: Using public Docker registry container
 
 ```yaml
 runs:
@@ -496,25 +385,18 @@ runs:
   image: 'docker://debian:stretch-slim'
 ```
 
-
-
-
 ### `runs.using`
 
 **必要** 必须将此值设置为 `'docker'`。
 
+### `runs.pre-entrypoint`
 
-
-### `pre-entrypoint`
-
-**可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `pre-entrypoint:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。
+**可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
 
 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
 在此示例中，`pre-entrypoint:` 操作会运行名为 `setup.sh` 的脚本：
 
-
-
 ```yaml
 runs:
   using: 'docker'
@@ -525,34 +407,23 @@ runs:
   entrypoint: 'main.sh'
 ```
 
-
-
-
 ### `runs.image`
 
 **必要** 要用作容器来运行操作的 Docker 映像。 值可以是 Docker 基本映像名称、仓库中的本地 `Dockerfile`、Docker Hub 中的公共映像或另一个注册表。 要引用仓库本地的 `Dockerfile`，文件必须命名为 `Dockerfile`，并且您必须使用操作元数据文件的相对路径。 `Docker` 应用程序将执行此文件。
 
-
-
 ### `runs.env`
 
 **可选** 指定要在容器环境中设置的环境变量的键/值映射。
 
-
-
 ### `runs.entrypoint`
 
 **可选** 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 当 `Dockerfile` 未指定 `ENTRYPOINT` 或者您想要覆盖 `ENTRYPOINT` 指令时使用 `entrypoint`。 如果您省略 `entrypoint`，您在 Docker `ENTRYPOINT` 指令中指定的命令将执行。 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。
 
 有关 `entrypoint` 如何执行的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)”。
 
-
-
 ### `post-entrypoint`
 
-**可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为  {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `post-entrypoint:` 操作始终默认运行，但您可以使用 [`post-if`](#post-if) 覆盖该设置。
-
-
+**可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为  {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
 
 ```yaml
 runs:
@@ -564,9 +435,6 @@ runs:
   post-entrypoint: 'cleanup.sh'
 ```
 
-
-
-
 ### `runs.args`
 
 **可选** 定义 Docker 容器输入的字符串数组。 输入可包含硬编码的字符串。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。
@@ -579,13 +447,9 @@ runs:
 
 有关将 `CMD` 指令与 {% data variables.product.prodname_actions %} 一起使用的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)”。
 
-
-
-#### 示例
+#### Example: Defining arguments for the Docker container
 
 {% raw %}
-
-
 ```yaml
 runs:
   using: 'docker'
@@ -595,21 +459,13 @@ runs:
     - 'foo'
     - 'bar'
 ```
-
-
 {% endraw %}
 
-
-
 ## `branding`
 
 您可以使用颜色和 [Feather](https://feathericons.com/) 图标创建徽章，以个性化和识别操作。 徽章显示在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作名称旁边。
 
-
-
-### 示例
-
-
+### Example: Configuring branding for an action
 
 ```yaml
 branding:
@@ -617,18 +473,18 @@ branding:
   color: 'green'
 ```
 
-
-
-
 ### `branding.color`
 
 徽章的背景颜色。 可以是以下之一：`white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple` 或 `gray-dark`。
 
-
-
 ### `branding.icon`
 
-要使用的 [Feather](https://feathericons.com/) 图标的名称。
+要使用的 [Feather](https://feathericons.com/) 图标的名称。 <!-- 
+  This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
+  This table does not match the latest version the feather library. 
+  (Brand icons are omitted, and our supported list is not necessarily up-to-date with the latest version of the feather icon library.)
+  To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo. 
+-->
 
 <table>
 <tr>
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
index 9d107bfd5d..84aeb6386d 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -29,7 +29,7 @@ By updating your workflows to use OIDC tokens, you can adopt the following good
 
 - **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC.
 - **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources.
-- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single workflow run, and then automatically expires.
+- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.
 
 ### Getting started with OIDC
 
@@ -38,7 +38,7 @@ The following diagram gives an overview of how {% data variables.product.prodnam
 ![OIDC diagram](/assets/images/help/images/oidc-architecture.png)
 
 1. In your cloud provider, create an OIDC trust between your cloud role and your {% data variables.product.prodname_dotcom %} workflow(s) that need access to the cloud.
-2. Every time your {% data variables.product.prodname_actions %} workflow job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
+2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate.
 3. You could include a step or action in your job to request this token from {% data variables.product.prodname_dotcom %}'s OIDC provider, and present it to the cloud provider.
 4. Once the cloud provider successfully validates the claims presented in the token, it then provides a short-lived cloud access token that is available only for the duration of the job.
 
@@ -51,7 +51,7 @@ When you configure your cloud to trust {% data variables.product.prodname_dotcom
 
 ### Understanding the OIDC token
 
-Each workflow run requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. During a workflow run, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
+Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition.
 
 The following example OIDC token uses a subject (`sub`) that references a job environment named `prod` in the `octo-org/octo-repo` repository.
 
@@ -147,7 +147,7 @@ In addition, your cloud provider could allow you to assign a role to the access
 
 ### 示例
 
-The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the workflow run's [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
+The following examples demonstrate how to use "Subject" as a condition. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use.
 
 #### Filtering for a specific environment
 
@@ -217,6 +217,10 @@ You could also use a `curl` command to request the JWT, using the following envi
 curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
 ```
 
+### Adding permissions settings
+
+{% data reusables.actions.oidc-permissions-token %}
+
 ## Updating your workflows for OIDC
 
 You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)."
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index 4558591372..df9ff468e3 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -56,14 +56,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
@@ -93,7 +86,7 @@ jobs:
       - name: Git clone the repository
         uses: actions/checkout@v2
       - name: configure aws credentials
-        uses: aws-actions/configure-aws-credentials@master
+        uses: aws-actions/configure-aws-credentials@v1
         with:
           role-to-assume: arn:aws:iam::1234567890:role/example-role
           role-session-name: samplerolesession
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 02cdcfad4a..ee6c4342fa 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -50,14 +50,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index ec4cab634d..d0823e7108 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -37,14 +37,7 @@ If your cloud provider doesn't yet offer an official action, you can update your
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Using official actions
 
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index 040ad59843..068cb10739 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -49,14 +49,7 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 90f8d11dcc..e2f45d1934 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -54,14 +54,7 @@ This example demonstrates how to use OIDC with the official action to request a
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
-
-```yaml{:copy}
-permissions:
-  id-token: write
-```
-
-You may need to specify additional permissions here, depending on your workflow's requirements.
+ {% data reusables.actions.oidc-permissions-token %}
 
 ### Requesting the access token
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index 8585b4c622..d2d43e5039 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -44,7 +44,7 @@ For more information about installing and using self-hosted runners, see "[Addin
 - Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes.
 
 **Self-hosted runners:**{% endif %}
-- Receive automatic updates for the self-hosted runner application only. You are responsible for updating the operating system and all other software. 
+- Receive automatic updates for the self-hosted runner application only{% ifversion fpt or ghec or ghes > 3.2 %}, though you may disable automatic updates of the runner. For more information about controlling runner software updates on self-hosted runners, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners#controlling-runner-software-updates-on-self-hosted-runners)."{% else %}.{% endif %} You are responsible for updating the operating system and all other software.
 - Can use cloud services or local machines that you already pay for.
 - Are customizable to your hardware, operating system, software, and security requirements.
 - Don't need to have a clean instance for every job execution.
@@ -55,7 +55,7 @@ For more information about installing and using self-hosted runners, see "[Addin
 You can use any machine as a self-hosted runner as long at it meets these requirements:
 
 * You can install and run the self-hosted runner application on the machine. For more information, see "[Supported architectures and operating systems for self-hosted runners](#supported-architectures-and-operating-systems-for-self-hosted-runners)."
-* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
+* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.product_name %}](#communication-requirements)."
 * The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
 * If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
 
@@ -125,6 +125,8 @@ Some extra configuration might be required to use actions from {% data variables
 
 {% endif %}
 
+<a name="communication-requirements"></a>
+
 ## Communication between self-hosted runners and {% data variables.product.product_name %}
 
 The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs.
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 78078cc6b8..2103cc051a 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -27,12 +27,12 @@ The following repositories have detailed instructions for setting up these autos
 
 Each solution has certain specifics that may be important to consider:
 
-| **功能**                         | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
-|:------------------------------ |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
-| Runtime                        | Kubernetes                                                                         | Linux and Windows VMs                                                 |
-| Supported Clouds               | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
-| Where runners can be scaled    | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
-| Pull-based autoscaling support | 是                                                                                  | 否                                                                     |
+| **功能**                      | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
+|:--------------------------- |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
+| Runtime                     | Kubernetes                                                                         | Linux and Windows VMs                                                 |
+| Supported Clouds            | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
+| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
+| How runners can be scaled   | Webhook events, Scheduled, Pull-based                                              | Webhook events, Scheduled (org-level runners only)                    |
 
 ## Using ephemeral runners for autoscaling
 
@@ -42,8 +42,8 @@ This approach allows you to manage your runners as ephemeral systems, since you
 
 To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. 例如：
 
-```
-$ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
+```shell
+./config.sh --url https://github.com/octo-org --token example-token --ephemeral
 ```
 
 The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered.
@@ -54,6 +54,28 @@ The {% data variables.product.prodname_actions %} service will then automaticall
 
 {% endnote %}
 
+## Controlling runner software updates on self-hosted runners
+
+By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available.  If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released.  Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
+
+If you want to turn off automatic software updates and install software updates yourself, you can specify the `--disableupdate` parameter when starting the runner.  例如：
+
+```shell
+./run.sh --disableupdate
+```
+
+If you disable automatic updates, you must still update your runner version regularly.  New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software.  The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
+
+If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available.  You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). 更多信息请参阅“[配置通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)”。
+
+For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
+
+{% note %}
+
+**Note:** If you do not perform a software update within 30 days, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner.  In addition, if a critical security update is required, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner until it has been updated.
+
+{% endnote %}
+
 ## Using webhooks for autoscaling
 
 You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 1de5cdf6e1..8621853dcd 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -33,6 +33,38 @@ shortTitle: Monitor & troubleshoot
     * **Active**: The runner is currently executing a job.
     * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}.
 
+## Checking self-hosted runner network connectivity
+
+You can use the self-hosted runner application's `run` script with the `--check` parameter to check that a self-hosted runner can access all required network services on {% data variables.product.product_location %}.
+
+In addition to `--check`, you must provide two arguments to the script:
+
+* `--url` with the URL to your {% data variables.product.company_short %} repository, organization, or enterprise. For example, `--url https://github.com/octo-org/octo-repo`.
+* `--pat` with the value of a personal access token, which must have the `workflow` scope. For example, `--pat ghp_abcd1234`. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+For example:
+
+{% mac %}
+
+{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+
+{% endmac %}
+{% linux %}
+
+{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
+
+{% endlinux %}
+{% windows %}
+
+```shell
+run.cmd --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
+```
+
+{% endwindows %}
+
+The script tests each service, and outputs either a `PASS` or `FAIL` for each one. If you have any failing checks, you can see more details on the problem in the log file for the check. The log files are located in the `_diag` directory where you installed the runner application, and the path of the log file for each check is shown in the console output of the script.
+
+If you have any failing checks, you should also verify that your self-hosted runner machine meets all the communication requirements. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)."
 
 ## Reviewing the self-hosted runner application log files
 
diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md
index c9ad4e1078..c9c954e663 100644
--- a/translations/zh-CN/content/actions/index.md
+++ b/translations/zh-CN/content/actions/index.md
@@ -32,7 +32,6 @@ featuredLinks:
     - title: GitHub Actions in action – Karan MV
       href: 'https://www.youtube-nocookie.com/embed/4SWO0Pc76CU'
   videosHeading: GitHub Universe 2021 videos
-examples_source: data/product-examples/actions/code-examples.yml
 product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
 redirect_from:
   - /articles/automating-your-workflow-with-github-actions
diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
index aa5311e698..fbbfb90a44 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
@@ -393,7 +393,7 @@ The `steps` context contains information about the steps in the current job that
 | 属性名称                                                | 类型    | 描述                                                                                                                                                                                                                                                                 |
 | --------------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `steps`                                             | `对象`  | 此上下文针对作业中的每个步骤而改变。 您可以从作业中的任何步骤访问此上下文。 This object contains all the properties listed below.                                                                                                                                                                       |
-| `steps.<step_id>.outputs`                     | `对象`  | 为步骤定义的输出集。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs)”。                                                                                                                                  |
+| `steps.<step_id>.outputs`                     | `对象`  | 为步骤定义的输出集。 For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."                                                      |
 | `steps.<step_id>.conclusion`                  | `字符串` | 在 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) 应用之后完成的步骤的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 当 `continue-on-error` 步骤失败时，`outcome` 为 `failure`，但最终的 `conclusion` 为 `success`。 |
 | `steps.<step_id>.outcome`                     | `字符串` | 在 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) 应用之前完成的步骤的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 当 `continue-on-error` 步骤失败时，`outcome` 为 `failure`，但最终的 `conclusion` 为 `success`。 |
 | `steps.<step_id>.outputs.<output_name>` | `字符串` | 特定输出的值。                                                                                                                                                                                                                                                            |
diff --git a/translations/zh-CN/content/actions/learn-github-actions/expressions.md b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
index 07bd7e05f7..0dc15fcbc3 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/expressions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
@@ -268,9 +268,15 @@ jobs:
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 ## 状态检查函数
 
 您可以使用以下状态检查函数作为 `if` 条件中的表达式。 除非您包含其中一个函数，否则 `success()` 的默认状态检查将会应用。 For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+{% else %}
+## Check Functions
+您可以使用以下状态检查函数作为 `if` 条件中的表达式。 除非您包含其中一个函数，否则 `success()` 的默认状态检查将会应用。 For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+{% endif %}
 
 ### success
 
@@ -318,6 +324,7 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 ### Evaluate Status Explicitly
 
 Instead of using one of the methods above, you can evaluate the status of the job or composite action that is executing the step directly:
@@ -343,6 +350,7 @@ steps:
 ```
 
 This is the same as using `if: failure()` in a composite action step.
+{% endif %}
 
 ## 对象过滤器
 
diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 074863bba3..a3e7f19973 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -47,6 +47,8 @@ topics:
 
 You can add an action to your workflow by referencing the action in your workflow file.
 
+You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
 ### Adding an action from {% data variables.product.prodname_marketplace %}
 
 操作的列表页包括操作的版本以及使用操作所需的工作流程语法。 为使工作流程在操作有更新时也保持稳定，您可以在工作流程文件中指定 Git 或 Docker 标记号以引用所用操作的版本。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
index c5e0e13e23..d983f2f1db 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
@@ -255,3 +255,8 @@ To understand how billing works for {% data variables.product.prodname_actions %
 ## 联系支持
 
 {% data reusables.github-actions.contacting-support %}
+
+## 延伸阅读
+
+{% ifversion ghec or ghes or ghae %}
+- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 73251e1496..d991634b40 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -18,16 +18,23 @@ shortTitle: 工作流程计费和限制
 
 ## 关于 {% data variables.product.prodname_actions %} 的计费
 
+{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.actions-billing %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
 {% else %}
-GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
+GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
 {% endif %}
 
+
+{% ifversion fpt or ghec %}
+
 ## 可用性
 
 {% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
 
+{% endif %}
+
 ## 使用限制
 
 {% ifversion fpt or ghec %}
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index 81510efac2..12d0714427 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -63,7 +63,7 @@ Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工
 | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                               | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                    | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                                                                                                                                                                                                                                                           |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                     | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore) <br> [<code>on.<pull_request\>.<branches\></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) |
 | [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                              | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | [Jenkins cron syntax](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                         | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
index fec3a19e0e..b3415aed02 100644
--- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
@@ -80,20 +80,20 @@ jobs:
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 下表显示默认情况下授予 `GITHUB_TOKEN` 的权限。 People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
 
-| 作用域                 | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br> |
-| ------------------- | ------------------ | ------------------ | ---------------------- |
-| 操作                  | 读/写                | 无                  | 读取                     |
-| 检查                  | 读/写                | 无                  | 读取                     |
-| 内容                  | 读/写                | 读取                 | 读取                     |
-| 部署                  | 读/写                | 无                  | 读取                     |
-| id-token            | 读/写                | 无                  | 读取                     |
-| 议题                  | 读/写                | 无                  | 读取                     |
-| 元数据                 | 读取                 | 读取                 | 读取                     |
-| 包                   | 读/写                | 无                  | 读取                     |
-| pull-requests       | 读/写                | 无                  | 读取                     |
-| repository-projects | 读/写                | 无                  | 读取                     |
-| security-events     | 读/写                | 无                  | 读取                     |
-| 状态                  | 读/写                | 无                  | 读取                     |
+| 作用域      | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br> |
+| -------- | ------------------ | ------------------ | ---------------------- |
+| 操作       | 读/写                | 无                  | 读取                     |
+| 检查       | 读/写                | 无                  | 读取                     |
+| 内容       | 读/写                | 读取                 | 读取                     |
+| 部署       | 读/写                | 无                  | 读取                     |
+| id-token | 读/写                | 无                  | 读取                     |
+| 议题       | 读/写                | 无                  | 读取                     |
+| 元数据      | 读取                 | 读取                 | 读取                     |
+| 包        | 读/写                | 无                  | 读取                     |
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-6187 %}
+| pages         | read/write  | none | read |
+{%- endif %}
+| pull-requests | read/write  | none | read | | repository-projects | read/write | none | read | | security-events     | read/write | none | read | | statuses      | read/write  | none | read |
 {% else %}
 | 作用域                 | 访问类型 | 通过复刻的仓库访问 |
 | ------------------- | ---- | --------- |
diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
index adeebbf68d..2ac8378243 100644
--- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
@@ -354,3 +354,50 @@ steps:
           run: cat $HOME/secrets/my_secret.json
   ```
 {% endraw %}
+
+
+## Storing Base64 binary blobs as secrets
+
+You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+
+{% note %}
+
+**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+
+{% endnote %}
+
+1. Use `base64` to encode your file into a Base64 string. 例如：
+
+   ```
+   $ base64 -i cert.der -o cert.base64
+   ```
+
+1. Create a secret that contains the Base64 string. 例如：
+
+   ```
+   $ gh secret set CERTIFICATE_BASE64 < cert.base64
+   ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
+   ```
+
+1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  例如：
+
+   ```yaml
+   name: Retrieve Base64 secret
+   on:
+     push:
+       branches: [ octo-branch ]
+   jobs:
+     decode-secret:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: actions/checkout@v2
+         - name: Retrieve the secret and decode it to a file
+           env:
+             {% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
+           run: |
+             echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
+         - name: Show certificate information
+           run: |
+             openssl x509 -in cert.der -inform DER -text -noout
+   ```
+
diff --git a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
index 7537d48ba4..19f48598a8 100644
--- a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -16,193 +16,9 @@ versions:
 shortTitle: 触发工作流程的事件
 ---
 
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## About events that trigger workflows
 
-## About workflow triggers
-
-Workflow triggers are events that cause a workflow to run. These events can be:
-
-- Events that occur in your workflow's repository
-- Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
-- Scheduled times
-- Manual
-
-For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.
-
-Workflow triggers are defined with the `on` key. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#on)”。
-
-以下步骤将触发工作流程运行：
-
-1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
-1. {% data variables.product.product_name %} searches the `.github/workflows` directory in your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
-
-1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
-
-  Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. 当工作流程运行时，{% data variables.product.product_name %} 会在运行器环境中设置 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF`（Git 引用）环境变量。 更多信息请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。
-
-### Triggering a workflow from a workflow
-
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
-
-If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 您需要创建个人访问令牌并将其存储为密码。 为了最大限度地降低 {% data variables.product.prodname_actions %} 使用成本，请确保不要创建递归或意外的工作流程。 For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
-
-For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
-
-```yaml
-on:
-  issues:
-    types:
-      - opened
-
-jobs:
-  label_issue:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.MY_TOKEN }}{% endraw %}
-          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
-        run: |
-          gh issue edit $ISSUE_URL --add-label "triage"
-```
-
-Conversely, the following workflow uses `GITHUB_TOKEN` to add a label to an issue. It will not trigger any workflows that run when a label is added.
-
-```yaml
-on:
-  issues:
-    types:
-      - opened
-
-jobs:
-  label_issue:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
-        run: |
-          gh issue edit $ISSUE_URL --add-label "triage"
-```
-
-## Using events to trigger workflows
-
-Use the `on` key to specify what events trigger your workflow. For more information about events you can use, see "[Available events](#available-events)" below.
-
-{% data reusables.github-actions.actions-on-examples %}
-
-## Using event information
-
-Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
-
-### Viewing all properties of an event
-
-Reference the webhook event documentation for common properties and example payloads. 更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)”。
-
-You can also print the entire `github.event` context to see what properties are available for the event that triggered your workflow:
-
-```yaml
-jobs:
-  print_context:
-    runs-on: ubuntu-latest
-    steps:
-      - env:
-          EVENT_CONTEXT: {% raw %}${{ toJSON(github.event) }}{% endraw %}
-        run: |
-          echo $EVENT_CONTEXT
-```
-
-### Accessing and using event properties
-
-You can use the `github.event` context in your workflow. For example, the following workflow runs when a pull request that changes `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**` is opened. If the pull request author (`github.event.pull_request.user.login`) is not `octobot` or `dependabot[bot]`, then the workflow uses the {% data variables.product.prodname_cli %} to label and comment on the pull request (`github.event.pull_request.number`).
-
-```yaml
-on:
-  pull_request:
-    types:
-      - opened
-    paths:
-      - '.github/workflows/**'
-      - '.github/CODEOWNERS'
-      - 'package*.json'
-
-jobs:
-  triage:
-    if: >-
-      github.event.pull_request.user.login != 'octobot' &&
-      github.event.pull_request.user.login != 'dependabot[bot]'
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Comment about changes we can't accept"
-        env:
-          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-          PR: {% raw %}${{ github.event.pull_request.html_url }}{% endraw %}
-        run: |
-          gh pr edit $PR --add-label 'invalid'
-          gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
-```
-
-For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
-
-## Further controlling how your workflow will run
-
-If you want more granular control than events, event activity types, or event filters provide, you can use conditionals{% ifversion fpt or ghae or ghes > 3.1 or ghec %} and environments{% endif %} to control whether individual jobs or steps in your workflow will run.
-
-### Using conditionals
-
-You can use conditionals to further control whether jobs or steps in your workflow will run. For example, if you want the workflow to run when a specific label is added to an issue, you can trigger on the `issues labeled` event activity type and use a conditional to check what label triggered the workflow. The following workflow will run when any label is added to an issue in the workflow's repository, but the `run_if_label_matches` job will only execute if the label is named `bug`.
-
-```yaml
-on:
-  issues:
-    types:
-      - labeled
-
-jobs:
-  run_if_label_matches:
-    if: github.event.label.name == 'bug'
-    runs-on: ubuntu-latest
-    steps:
-      - run: echo 'The label was bug'
-```
-
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
-
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Using environments to manually trigger workflow jobs
-
-If you want to manually trigger a specific job in a workflow, you can use an environment that requires approval from a specific team or user. First, configure an environment with required reviewers. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." Then, reference the environment name in a job in your workflow using the `environment:` key. Any job referencing the environment will not run until at least one reviewer approves the job.
-
-For example, the following workflow will run whenever there is a push to main. The `build` job will always run. The `publish` job will only run after the `build` job successfully completes (due to `needs: [build]`) and after all of the rules (including required reviewers) for the environment called `production` pass (due to `environment: production`).
-
-```yaml
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: build
-        echo 'building'
-
-  publish:
-    needs: [build]
-    runs-on: ubuntu-latest
-    environment: production
-    steps:
-      - name: publish
-        echo 'publishing'
-```
-
-{% note %}
-
-{% data reusables.gated-features.environments %}
-
-{% endnote %}
-{% endif %}
+Workflow triggers are events that cause a workflow to run. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
 
 ## Available events
 
@@ -794,7 +610,7 @@ jobs:
 
 #### Running your workflow based on the head or base branch of a pull request
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)”。
 
 For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
 
@@ -841,7 +657,7 @@ jobs:
 
 #### Running your workflow based on files changed in a pull request
 
-You can also configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can also configure your workflow to run when a pull request changes specific files. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)”。
 
 For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
 
@@ -978,7 +794,7 @@ on:
 
 #### Running your workflow based on the head or base branch of a pull request
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)”。
 
 For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
 
@@ -1025,7 +841,7 @@ jobs:
 
 #### Running your workflow based on files changed in a pull request
 
-You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)”。
 
 For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
 
@@ -1082,7 +898,7 @@ on:
 
 #### Running your workflow only when a push to specific branches occurs
 
-You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)”。
 
 For example, this workflow will run when someone pushes to `main` or to a branch that starts with `releases/`.
 
@@ -1113,7 +929,7 @@ on:
 
 #### Running your workflow only when a push of specific tags occurs
 
-You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags or are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags or are pushed. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)”。
 
 For example, this workflow will run when someone pushes a tag that starts with `v1.`.
 
@@ -1126,7 +942,7 @@ on:
 
 #### Running your workflow only when a push affects specific files
 
-You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a push to specific files occurs. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a push to specific files occurs. 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)”。
 
 For example, this workflow will run when someone pushes a change to a JavaScript file (`.js`):
 
@@ -1168,7 +984,7 @@ on:
 
 {% data reusables.github-actions.branch-requirement %}
 
-Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. For more information, see "[{% data variables.product.prodname_registry %} Documentation](/packages)."
+Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. 更多信息请参阅“[{% data variables.product.prodname_registry %} 文档](/packages)”。
 
 例如，您可以在软件包为 `published` 时运行工作流程。
 
@@ -1220,7 +1036,7 @@ on:
 
 {% data reusables.github-actions.branch-requirement %}
 
-You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.product_name %}. 更多信息请参阅“[创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)”。
+当您想要触发在 {% data variables.product.product_name %} 外发生的活动的工作流程时，可以使用 {% data variables.product.product_name %} API 触发名为 [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) 的 web 挂钩事件。 更多信息请参阅“[创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)”。
 
 When you make a request to create a `repository_dispatch` event, you must specify an `event_type` to describe the activity type. By default, all `repository_dispatch`  activity types trigger a workflow to run. You can use the `types` keyword to limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload.
 
@@ -1371,7 +1187,7 @@ on:
 | --------------------------- | ---- | --------------------------- | --------------------------- |
 | Same as the caller workflow | n/a  | Same as the caller workflow | Same as the caller workflow |
 
-`workflow_call` is used to indicate that a workflow can be called by another workflow. When a workflow is triggered with the `workflow_call` event, the event playload in the called workflow is the same event payload from the calling workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+`workflow_call` is used to indicate that a workflow can be called by another workflow. When a workflow is triggered with the `workflow_call` event, the event payload in the called workflow is the same event payload from the calling workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 
 The example below only runs the workflow when it's called from another workflow:
 
diff --git a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
index faa456a49e..8a82e0c89d 100644
--- a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md
@@ -34,6 +34,8 @@ If you reuse a workflow from a different repository, any actions in the called w
 
 When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
 
+You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
 ### Reusable workflows and starter workflows
 
 Starter workflows allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Within a starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
@@ -110,7 +112,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
        runs-on: ubuntu-latest
        environment: production
        steps:
-         - uses: ./.github/actions/my-action@v1
+         - uses: ./.github/actions/my-action
            with:
              username: ${{ inputs.username }}
              token: ${{ secrets.envPAT }}
@@ -151,7 +153,7 @@ jobs:
     name: Pass input and secrets to my-action
     runs-on: ubuntu-latest
     steps:
-      - uses: ./.github/actions/my-action@v1
+      - uses: ./.github/actions/my-action
         with:
           username: ${{ inputs.username }}
           token: ${{ secrets.token }}
diff --git a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
index b8d22a819e..4530092d78 100644
--- a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md
@@ -12,36 +12,242 @@ topics:
   - Workflows
   - CI
   - CD
-miniTocMaxHeadingLevel: 4
+miniTocMaxHeadingLevel: 3
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 概览
+## About workflow triggers
 
-{% data reusables.actions.workflows.section-triggering-a-workflow %}
+Workflow triggers are events that cause a workflow to run. These events can be:
 
-## Defining event types
+- Events that occur in your workflow's repository
+- Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
+- Scheduled times
+- Manual
 
-{% data reusables.actions.workflows.section-triggering-a-workflow-types %}
+For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.
 
-## 定向特定分支
+Workflow triggers are defined with the `on` key. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#on)”。
+
+以下步骤将触发工作流程运行：
+
+1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
+1. {% data variables.product.product_name %} searches the `.github/workflows` directory in your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
+1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
+
+  Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. 当工作流程运行时，{% data variables.product.product_name %} 会在运行器环境中设置 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF`（Git 引用）环境变量。 更多信息请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。
+
+### Triggering a workflow from a workflow
+
+{% data reusables.github-actions.actions-do-not-trigger-workflows %} 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
+
+If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. 您需要创建个人访问令牌并将其存储为密码。 为了最大限度地降低 {% data variables.product.prodname_actions %} 使用成本，请确保不要创建递归或意外的工作流程。 For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.MY_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+Conversely, the following workflow uses `GITHUB_TOKEN` to add a label to an issue. It will not trigger any workflows that run when a label is added.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+## Using events to trigger workflows
+
+Use the `on` key to specify what events trigger your workflow. For more information about events you can use, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+
+### Using a single event
+
+{% data reusables.github-actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.github-actions.on-multiple-example %}
+
+### Using activity types and filters with multiple events
+
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
+
+## Using event activity types
+
+{% data reusables.github-actions.actions-activity-types %}
+
+## Using filters
+
+{% data reusables.github-actions.actions-filters %}
+
+### Using filters to target specific branches for pull request events
 
 {% data reusables.actions.workflows.section-triggering-a-workflow-branches %}
 
-## Running on specific branches or tags
+### Using filters to target specific branches or tags for push events
 
 {% data reusables.actions.workflows.section-run-on-specific-branches-or-tags %}
 
-## Specifying which branches the workflow can run on
-
-{% data reusables.actions.workflows.section-specifying-branches %}
-
-## Using specific file paths
+### Using filters to target specific paths for pull request or push events
 
 {% data reusables.actions.workflows.section-triggering-a-workflow-paths %}
 
-## Using a schedule
+### Using filters to target specific branches for workflow run events
 
-{% data reusables.actions.workflows.section-triggering-a-workflow-schedule %}
+{% data reusables.actions.workflows.section-specifying-branches %}
+
+## Defining inputs for manually triggered workflows
+
+{% data reusables.github-actions.workflow-dispatch-inputs %}
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+## Defining inputs, outputs, and secrets for reusable workflows
+
+You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+
+{% endif %}
+
+## Using event information
+
+Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
+
+### Viewing all properties of an event
+
+Reference the webhook event documentation for common properties and example payloads. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+You can also print the entire `github.event` context to see what properties are available for the event that triggered your workflow:
+
+```yaml
+jobs:
+  print_context:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          EVENT_CONTEXT: {% raw %}${{ toJSON(github.event) }}{% endraw %}
+        run: |
+          echo $EVENT_CONTEXT
+```
+
+### Accessing and using event properties
+
+You can use the `github.event` context in your workflow. For example, the following workflow runs when a pull request that changes `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**` is opened. If the pull request author (`github.event.pull_request.user.login`) is not `octobot` or `dependabot[bot]`, then the workflow uses the {% data variables.product.prodname_cli %} to label and comment on the pull request (`github.event.pull_request.number`).
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    paths:
+      - '.github/workflows/**'
+      - '.github/CODEOWNERS'
+      - 'package*.json'
+
+jobs:
+  triage:
+    if: >-
+      github.event.pull_request.user.login != 'octobot' &&
+      github.event.pull_request.user.login != 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: "Comment about changes we can't accept"
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          PR: {% raw %}${{ github.event.pull_request.html_url }}{% endraw %}
+        run: |
+          gh pr edit $PR --add-label 'invalid'
+          gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
+```
+
+For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+## Further controlling how your workflow will run
+
+If you want more granular control than events, event activity types, or event filters provide, you can use conditionals{% ifversion fpt or ghae or ghes > 3.1 or ghec %} and environments{% endif %} to control whether individual jobs or steps in your workflow will run.
+
+### Using conditionals
+
+You can use conditionals to further control whether jobs or steps in your workflow will run. For example, if you want the workflow to run when a specific label is added to an issue, you can trigger on the `issues labeled` event activity type and use a conditional to check what label triggered the workflow. The following workflow will run when any label is added to an issue in the workflow's repository, but the `run_if_label_matches` job will only execute if the label is named `bug`.
+
+```yaml
+on:
+  issues:
+    types:
+      - labeled
+
+jobs:
+  run_if_label_matches:
+    if: github.event.label.name == 'bug'
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo 'The label was bug'
+```
+
+For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+
+### Using environments to manually trigger workflow jobs
+
+If you want to manually trigger a specific job in a workflow, you can use an environment that requires approval from a specific team or user. First, configure an environment with required reviewers. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." Then, reference the environment name in a job in your workflow using the `environment:` key. Any job referencing the environment will not run until at least one reviewer approves the job.
+
+For example, the following workflow will run whenever there is a push to main. The `build` job will always run. The `publish` job will only run after the `build` job successfully completes (due to `needs: [build]`) and after all of the rules (including required reviewers) for the environment called `production` pass (due to `environment: production`).
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: build
+        echo 'building'
+
+  publish:
+    needs: [build]
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: publish
+        echo 'publishing'
+```
+
+{% note %}
+
+{% data reusables.gated-features.environments %}
+
+{% endnote %}
+{% endif %}
+
+## Available events
+
+For a full list of available events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 2bf4229bfe..815e9b82be 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -92,7 +92,7 @@ core.setOutput('SELECTED_COLOR', 'green');
 
 设置操作的输出参数。
 
-（可选）您也可以在操作的元数据文件中声明输出参数。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs)”。
+（可选）您也可以在操作的元数据文件中声明输出参数。 For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
 
 ### 示例
 
@@ -292,7 +292,7 @@ Only the second `set-output` and `echo` workflow commands are included in the lo
 
 您可以使用 `save-state` 命令来创建环境变量，以便与工作流程的 `pre:` 或 `post:` 操作共享。 例如，您可以使用 `pre:` 操作创建文件，将该文件位置传给 `main:` 操作，然后使用 `post:` 操作删除文件。 或者，您可以使用 `main:` 操作创建文件，将该文件位置传给 `post:` 操作，然后使用 `post:` 操作删除文件。
 
-如果您有多个 `pre:` 或 `post:` 操作，则只能访问使用了 `save-state` 的操作中的已保存值。 有关 `post:` 操作的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions#post)”。
+如果您有多个 `pre:` 或 `post:` 操作，则只能访问使用了 `save-state` 的操作中的已保存值。 有关 `post:` 操作的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions#runspost)”。
 
 `save-state` 命令只能在操作内运行，并且对 YAML 文件不可用。 保存的值将作为环境值存储，带 `STATE_` 前缀。
 
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 8a1db6c9e3..02d9f85a3b 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -149,7 +149,7 @@ jobs:
 
     steps:
       - name: Pass the received secret to an action
-        uses: ./.github/actions/my-action@v1
+        uses: ./.github/actions/my-action
         with:
           token: ${{ secrets.access-token }}
 ```
@@ -171,42 +171,7 @@ A boolean specifying whether the secret must be supplied.
 
 ## `on.workflow_dispatch.inputs`
 
-When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
-
-触发的工作流程接收 `github.event.input` 上下文中的输入。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。
-
-### 示例
-```yaml
-on:
-  workflow_dispatch:
-    inputs:
-      logLevel:
-        description: 'Log level'
-        required: true
-        default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
-        type: choice
-        options:
-        - info
-        - warning
-        - debug {% endif %}
-      tags:
-        description: 'Test scenario tags'
-        required: false {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
-        type: boolean
-      environment:
-        description: 'Environment to run tests against'
-        type: environment
-        required: true {% endif %}
-
-jobs:
-  print-tag:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Print the input tag to STDOUT
-        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
-```
-
+{% data reusables.github-actions.workflow-dispatch-inputs %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `权限`
@@ -1008,7 +973,7 @@ For more information about branch, tag, and path filter syntax, see "[`on.<push>
 | `'**'`                                                  | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。                   | `all/the/branches`<br/><br/>`every/tag`                                                                   |
 | `'*feature'`                                            | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。                           | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
 | `v2*`                                                   | 匹配以 `v2` 开头的分支和标记名称。                                                 | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
-| `v[12].[0-9]+.[0-9]+`                                   | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配                                         | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
+| `v[12].[0-9]+.[0-9]+`                                   | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配.                                        | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
 ### 匹配文件路径的模式
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
index a5bab1c756..d8441be833 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -38,6 +38,8 @@ topics:
 
 ## 上传自定义 TLS 证书
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
@@ -67,6 +69,8 @@ Let's Encrypt 是公共证书颁发机构，他们使用 ACME 协议颁发受浏
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 7a347ea3ce..afe9132dfc 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -136,5 +136,5 @@ $ ghe-restore -c 169.154.1.1
 {% endnote %}
 
 You can use these additional options with `ghe-restore` command:
-- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
 - The `-s` flag allows you to select a different backup snapshot.
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index e0987ad337..8f9f359c87 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -88,8 +88,7 @@ settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-all
 4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery).
 5. When the test email succeeds, at the bottom of the page, click **Save settings**.
 ![Save settings button](/assets/images/enterprise/management-console/save-settings.png)
-6. Wait for the configuration run to complete.
-![Configuring your instance](/assets/images/enterprise/management-console/configuration-run.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
 
 ## Configuring DNS and firewall settings to allow incoming emails
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index a90586c766..de18025f1a 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -47,7 +47,7 @@ topics:
 
 ## 使用 `ghe-export-graphs` 导出 collectd 数据
 
-命令行工具 `ghe-export-graphs` 将导出 `collectd` 存储在 RRD 数据库中的数据。 此命令会将数据转换为 XML 格式并导出到一个 tarball (.tgz) 中。
+命令行工具 `ghe-export-graphs` 将导出 `collectd` 存储在 RRD 数据库中的数据。 This command turns the data into XML and exports it into a single tarball (`.tgz`).
 
 此文件的主要用途是为 {% data variables.contact.contact_ent_support %} 团队提供关于 VM 性能的数据（无需下载整个支持包）， 不应包含在常规备份导出范围中，也没有对应的导入文件。 如果您联系 {% data variables.contact.contact_ent_support %}，我们可能会要求您提供此数据，以便协助故障排查。
 
diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index eeae6fb8a8..be6dc809eb 100644
--- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -52,9 +52,11 @@ If you use Docker container actions or service containers in your workflows, you
 
 If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
 
-## Runners not connecting to {% data variables.product.prodname_ghe_server %} after changing the hostname
+## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
 
-If you change the hostname of {% data variables.product.product_location %}, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
 
 You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.product.product_location %}. Each self-hosted runner will require one of the following procedures:
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
new file mode 100644
index 0000000000..2845c1a179
--- /dev/null
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -0,0 +1,42 @@
+---
+title: About GitHub Actions for enterprises
+shortTitle: 关于 GitHub Actions
+intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+With {% data variables.product.prodname_actions %}, you can improve developer productivity by automating every phase of your enterprise's software development workflow.
+
+| 任务                                                                    | 更多信息                                                                                                                                                                   |
+| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Automatically test and build your application                         | "[关于持续集成](/actions/automating-builds-and-tests/about-continuous-integration)"                                                                                          |
+| Deploy your application                                               | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)"                                                                     |
+| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)"                               |
+| Automate your project management tasks                                | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+
+{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
+
+{% data variables.product.prodname_actions %} also provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. This will allow you to stop storing credentials as long-lived secrets and provide other security benefits. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
+{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
+
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. 更多信息请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。
+
+{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)”。
+
+
+To learn more about how you can successfully adopt {% data variables.product.prodname_actions %} for your enterprise, follow the "[Adopt {% data variables.product.prodname_actions %} for your enterprise](/admin/guides#adopt-github-actions-for-your-enterprise)" learning path.
+
+## 延伸阅读
+
+- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
+- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 09f91b2a8c..c0cac4ebb7 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -9,6 +9,7 @@ topics:
   - Enterprise
   - Actions
 children:
+  - /about-github-actions-for-enterprises
   - /introducing-github-actions-to-your-enterprise
   - /migrating-your-enterprise-to-github-actions
   - /getting-started-with-github-actions-for-github-enterprise-cloud
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index db4ad2c263..01341eb374 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -14,7 +14,7 @@ topics:
 
 ## About {% data variables.product.prodname_actions %} for enterprises
 
-{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
 
 ![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
 
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index 9b58a1b10e..d9570bb938 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -178,7 +178,7 @@ topics:
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 3. 在左侧边栏中，单击 **LDAP users**。 ![LDAP users 选项卡](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. 要搜索用户，请输入完整或部分用户名，然后单击 **Search**。 现有用户将显示在搜索结果中。 如果用户不存在，请单击 **Create** 以配置新用户帐户。 ![LDAP 搜索](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
+4. 要搜索用户，请输入完整或部分用户名，然后单击 **Search**。 现有用户将显示在搜索结果中。 如果用户不存在，请单击 **Create** 以配置新用户帐户。 ![LDAP 搜索](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg)
 
 ## 更新 LDAP 帐户
 
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 869ed4782d..3b86021a4a 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -47,6 +47,7 @@ redirect_from:
 | -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
 | Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
 | Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| Okta                                         | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
 | OneLogin                                     | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | PingOne                                      | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
 | Shibboleth                                   | {% octicon "check-circle-fill" aria-label="The check icon" %}  |                                                               |
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index 1ffb15be43..048323516d 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -15,8 +15,6 @@ redirect_from:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
-{% data reusables.enterprise-accounts.emu-saml-note %}
-
 ## 关于企业帐户的 SAML 单点登录
 
 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md
index c7893c6b87..7b8cedcc2b 100644
--- a/translations/zh-CN/content/admin/index.md
+++ b/translations/zh-CN/content/admin/index.md
@@ -97,12 +97,14 @@ featuredLinks:
     - '{% ifversion ghes %}/admin/installation{% endif %}'
     - '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
     - '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
     - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
     - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
+    - /admin/configuration/configuring-github-connect/managing-github-connect
     - /admin/enterprise-support/about-github-enterprise-support
   videos:
     - title: "GitHub in the Enterprise – Maya Ross"
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 0753d7ca8e..82d6d08977 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -40,12 +40,12 @@ shortTitle: 在 Azure 上安装
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. 找到最新的 {% data variables.product.prodname_ghe_server %} 设备映像。 更多关于 `vm image list` 命令的信息，请参阅 Microsoft 文档中的“[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)”。
+1. 找到最新的 {% data variables.product.prodname_ghe_server %} 设备映像。 For more information about the `vm image list` command, see "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. 使用找到的设备映像创建新的 VM。 更多信息请参阅 Microsoft 文档中的“[az vm 创建](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)”。
+2. 使用找到的设备映像创建新的 VM。 For more information, see "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
 
   传入以下选项：VM 名称、资源组、VM 大小、首选 Azure 地区名称、上一步中列出的设备映像 VM 的名称，以及用于高级存储的存储 SKU。 更多关于资源组的信息，请参阅 Microsoft 文档中的“[资源组](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)”。
 
@@ -53,7 +53,7 @@ shortTitle: 在 Azure 上安装
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. 在 VM 上配置安全设置，以打开所需端口。 更多信息请参阅 Microsoft 文档中的 "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)"。 请参阅下表中对每个端口的说明，以确定需要打开的端口。
+3. 在 VM 上配置安全设置，以打开所需端口。 For more information, see "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. 请参阅下表中对每个端口的说明，以确定需要打开的端口。
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
@@ -63,7 +63,7 @@ shortTitle: 在 Azure 上安装
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
+4. 创建新的未加密数据磁盘并将其附加至 VM，然后根据用户许可数配置大小。 For more information, see "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
 
   传入以下选项：VM 名称（例如 `ghe-acme-corp`）、资源组、高级存储 SKU、磁盘大小（例如 `100`）以及生成的 VHD 的名称。
 
@@ -79,7 +79,7 @@ shortTitle: 在 Azure 上安装
 
 ## 配置 {% data variables.product.prodname_ghe_server %} 虚拟机
 
-1. 在配置 VM 之前，您必须等待其进入 ReadyRole 状态。 使用 `vm list` 命令检查 VM 的状态。 更多信息请参阅 Microsoft 文档中的“[az vm 列表](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)”。
+1. 在配置 VM 之前，您必须等待其进入 ReadyRole 状态。 使用 `vm list` 命令检查 VM 的状态。 For more information, see "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
diff --git a/translations/zh-CN/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/zh-CN/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
new file mode 100644
index 0000000000..63768a7538
--- /dev/null
+++ b/translations/zh-CN/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your enterprise
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Enterprise owners can access compliance reports for the enterprise.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your enterprise settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## 延伸阅读
+
+- "[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
diff --git a/translations/zh-CN/content/admin/overview/index.md b/translations/zh-CN/content/admin/overview/index.md
index b16bd3201a..3d331c28e9 100644
--- a/translations/zh-CN/content/admin/overview/index.md
+++ b/translations/zh-CN/content/admin/overview/index.md
@@ -15,6 +15,7 @@ children:
   - /system-overview
   - /about-the-github-enterprise-api
   - /creating-an-enterprise-account
+  - /accessing-compliance-reports-for-your-enterprise
 ---
 
 如需了解更多信息或购买 {% data variables.product.prodname_enterprise %}，请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise)。
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 1dfc8445ab..eab2fd84a1 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -100,6 +100,10 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index f4108863c8..75a5107565 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -146,9 +146,8 @@ You can use a SSH certificate authorities (CA) to allow members of any organizat
 {% data reusables.organizations.delete-ssh-ca %}
 
 {% ifversion ghec or ghae %}
-
 ## 延伸阅读
 
-- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
-
+- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
 {% endif %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 48b09b3704..182e146c8e 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -90,6 +90,9 @@ The `$GITHUB_VIA` variable is available in the pre-receive hook environment when
 | <pre>git refs delete api</pre> | Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation |
 | <pre>git refs update api</pre> | Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation |
 | <pre>git repo contents api</pre> | Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation |
+{%- ifversion ghes > 3.0 %}
+| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
 | <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" |
 | <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
 | <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" |
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index 9431452c4f..ad14b7c8e6 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -9,6 +9,7 @@ redirect_from:
 intro: '创建团队后，组织管理员可以将用户从 {% data variables.product.product_location %} 添加到团队并决定他们可以访问哪些仓库。'
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -30,8 +31,12 @@ topics:
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
+{% ifversion ghes %}
+
 ## 将团队映射到 LDAP 组（例如，使用 LDAP 同步进行用户身份验证）
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
 要将新成员添加到已同步至 LDAP 组的团队，请将用户添加为 LDAP 组的成员，或者联系您的 LDAP 管理员。
+
+{% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
index 67919f01d1..f9639cf047 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
@@ -7,6 +7,7 @@ redirect_from:
   - /admin/user-management/continuous-integration-using-jenkins
 versions:
   ghes: '*'
+  ghae: '*'
 type: reference
 topics:
   - CI
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
index 52334965f2..e638566bb1 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/creating-teams
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -32,6 +33,8 @@ A prudent combination of teams is a powerful way to control repository access. F
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
 
+{% ifversion ghes %}
+
 ## Creating teams with LDAP Sync enabled
 
 Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.product.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
@@ -60,3 +63,5 @@ You must be a site admin and an organization owner to create a team with LDAP sy
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% data reusables.organizations.create_team %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 6bda13ac8c..0514cbc874 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
 title: 使用 Jira 管理项目
-intro: '您可以将 Jira 与 {% data variables.product.prodname_enterprise %} 集成以进行项目管理。'
+intro: '您可以将 Jira 与 {% data variables.product.product_name %} 集成以进行项目管理。'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira
   - /enterprise/admin/articles/project-management-using-jira
@@ -10,6 +10,7 @@ redirect_from:
   - /admin/user-management/managing-projects-using-jira
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
index 4c45eaf21f..734bd86ad4 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
@@ -6,6 +6,7 @@ redirect_from:
   - /admin/user-management/removing-users-from-teams-and-organizations
 versions:
   ghes: '*'
+  ghae: '*'
 type: how_to
 topics:
   - Access management
@@ -25,6 +26,8 @@ shortTitle: 删除用户成员资格
 
 ## 移除团队成员
 
+{% ifversion ghes %}
+
 {% warning %}
 
 **注**：{% data reusables.enterprise_management_console.badge_indicator %}
@@ -33,6 +36,8 @@ shortTitle: 删除用户成员资格
 
 {% endwarning %}
 
+{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index 0394f5aa69..18acc84060 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -15,7 +15,7 @@ shortTitle: 管理支持权利
 
 拥有企业帐户支持权限的人员可以使用支持门户打开、查看和评论与企业帐户相关的支持事件单。
 
-企业所有人和帐单管理员自动拥有支持权利。 企业所有者可以向企业帐户拥有的组织成员添加支持权利。
+企业所有人和帐单管理员自动拥有支持权利。 Enterprise owners can add support entitlements to up to 20 additional members of organizations owned by their enterprise account.
 
 ## 向企业成员添加支持权利
 
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index 78768940fc..395133a045 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -26,7 +26,7 @@ topics:
 {% ifversion ghes %}
 ## 系统事件
 
-所有经过审核的系统事件（包括所有推送和拉取）都会记录到 `/var/log/github/audit.log` 中。 日志每 24 小时自动轮换一次，并会保留七天。
+All audited system events are logged to `/var/log/github/audit.log`. 日志每 24 小时自动轮换一次，并会保留七天。
 
 支持包中包含系统日志。 更多信息请参阅“[向 {% data variables.product.prodname_dotcom %} Support 提供数据](/admin/enterprise-support/providing-data-to-github-support)”。
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 4d6923a4ef..9218ddf5b7 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -8,6 +8,7 @@ redirect_from:
   - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
   - /github/authenticating-to-github/creating-a-personal-access-token
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
+  - /github/extending-github/git-automation-with-oauth-tokens
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index 8602712bde..cabcaf41d5 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -18,7 +18,11 @@ shortTitle: 部署密钥
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
 3. 在左侧边栏中，单击 **Deploy keys（部署密钥）**。 ![部署密钥设置](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
 4. 在 Deploy keys（部署密钥）页面中，记下与您的帐户关联的部署密钥。 对于您无法识别或已过期的密钥，请单击 **Delete（删除）**。 如果有您要保留的有效部署密钥，请单击 **Approve（批准）**。 ![部署密钥列表](/assets/images/help/settings/settings-deploy-key-review.png)
 
 更多信息请参阅“[管理部署密钥](/guides/managing-deploy-keys)”。
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 4291740168..319efc5029 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -22,12 +22,10 @@ shortTitle: 安全日志
 安全日志列出了过去 90 天内执行的所有操作。
 
 {% data reusables.user_settings.access_settings %}
-{% ifversion fpt or ghae or ghes or ghec %}
-2. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 ![安全日志选项卡](/assets/images/help/settings/audit-log-tab.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
 {% else %}
-{% data reusables.user_settings.security %}
-3. 在“Security history（安全历史记录）”下，将显示您的日志。 ![安全日志](/assets/images/help/settings/user_security_log.png)
-4. 单击条目以查看有关该事件的更多信息。 ![安全日志](/assets/images/help/settings/user_security_history_action.png)
+1. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 ![安全日志选项卡](/assets/images/help/settings/audit-log-tab.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
index 3ae2cce8ea..cb74b34061 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -33,7 +33,7 @@ $ ssh -T -p 443 git@ssh.github.com
 
 如果您能在端口 443 上通过 SSH 连接到 `git@ssh.{% data variables.command_line.backticks %}`，则可以覆盖您的 SSH 设置以强制与 {% data variables.product.product_location %} 的任何连接均通过该服务器和端口运行。
 
-要在您的 ssh 配置中设置此项，编辑位于 `~/.ssh/config` 的文件，添加以下部分：
+To set this in your SSH confifguration file, edit the file at `~/.ssh/config`, and add this section:
 
 ```
 Host {% data variables.command_line.codeblock %}
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 12262b9e92..c7fb9f89ff 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -37,6 +37,10 @@ If you want to view an overview of your subscription and usage for {% data varia
 
 ## 查看企业帐户的订阅和使用情况
 
+You can view the subscription and usage for your enterprise and download a file with license details.
+
+{% data reusables.billing.license-statuses %}
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/about-billing-on-github.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
index a0250ab23a..355ecead59 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
@@ -36,7 +36,7 @@ topics:
 {% data reusables.user_settings.access_settings %}
 1. 在页面顶部用户名的右侧，单击 **Switch to another account（切换到另一个帐户）**。 ![上下文切换器按钮](/assets/images/help/settings/context-switcher-button.png)
 1. 开始键入要切换到的帐户名称，然后单击帐户的名称。 ![上下文切换器菜单](/assets/images/help/settings/context-switcher-menu.png)
-1. 在左侧边栏中，单击 **Billing & plans（计费和方案）**。 ![设置侧边栏中的计费和方案](/assets/images/help/organizations/billing-settings.png)
+1. In the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
index 5afb0ad8e4..7f1a13798f 100644
--- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
@@ -30,6 +30,10 @@ You can view license usage for {% data variables.product.prodname_ghe_server %}
 
 ## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}
 
+You can view the license usage for your enterprise and download a file with license details.
+
+{% data reusables.billing.license-statuses %}
+
 {% ifversion ghec %}
 
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
new file mode 100644
index 0000000000..9d6c9f02dc
--- /dev/null
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
@@ -0,0 +1,119 @@
+---
+title: About code scanning alerts
+intro: Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## 关于 {% data variables.product.prodname_code_scanning %} 中的警报
+
+您可以设置 {% data variables.product.prodname_code_scanning %}，以使用默认 {% data variables.product.prodname_codeql %} 分析、第三方分析或多种类型的分析来检查仓库中的代码。 分析完成后，生成的警报将并排显示在仓库的安全视图中。 第三方工具或自定义查询的结果可能不包括您在 {% data variables.product.company_short %} 的默认 {% data variables.product.prodname_codeql %} 分析所检测的警报中看到的所有属性。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
+
+默认情况下， {% data variables.product.prodname_code_scanning %} 定期在默认分支和拉取请求中分析您的代码。 有关管理拉取请求中的警报的更多信息，请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。
+
+## About alert details
+
+每个警报都会高亮显示代码的问题以及识别该问题的工具名称。 You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. 警报还会告知该问题第一次被引入的时间。 对于由 {% data variables.product.prodname_codeql %} 分析确定的警报，您还会看到如何解决问题的信息。
+
+![来自 {% data variables.product.prodname_code_scanning %} 的警报示例](/assets/images/help/repository/code-scanning-alert.png)
+
+If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. 数据流分析将查找代码中的潜在安全问题，例如：不安全地使用数据、将危险参数传递给函数以及泄漏敏感信息。
+
+当 {% data variables.product.prodname_code_scanning %} 报告数据流警报时，{% data variables.product.prodname_dotcom %} 将显示数据在代码中如何移动。 {% data variables.product.prodname_code_scanning_capc %} 可用于识别泄露敏感信息的代码区域，以及可能成为恶意用户攻击切入点的代码区域。
+
+### About severity levels
+
+Alert severity levels may be `Error`, `Warning`, or `Note`.
+
+If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+### About security severity levels
+
+{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
+
+To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
+
+By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
+
+### About labels for alerts that are not found in application code
+
+{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
+
+- **Generated**: Code generated by the build process
+- **Test**: Test code
+- **Library**: Library or third-party code
+- **Documentation**: Documentation
+
+{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
+
+Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
+
+![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
+
+On the alert page, you can see that the filepath is marked as library code (`Library` label).
+
+![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
+
+{% if codeql-ml-queries %}
+
+## About experimental alerts
+
+{% data reusables.code-scanning.beta-codeql-ml-queries %}
+
+In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
+
+![Code scanning experimental alert in list](/assets/images/help/repository/code-scanning-experimental-alert-list.png)
+
+### Benefits of using machine learning models to extend queries
+
+Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
+
+Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
+
+{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
+
+### Alerts identified using machine learning
+
+Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
+
+![Code scanning experimental alert details](/assets/images/help/repository/code-scanning-experimental-alert-show.png)
+
+## Enabling experimental alerts
+
+The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you update your workflow to run an additional query suite this will increase the analysis time.
+
+``` yaml
+- uses: github/codeql-action/init@v1
+  with:
+    # Run extended queries including queries using machine learning
+    queries: security-extended
+```
+
+更多信息请参阅“[配置代码扫描](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)”。
+
+## Disabling experimental alerts
+
+The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
+
+- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
+- Specify details of the repositories or organizations that are affected
+- Request an escalation to engineering
+
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index 1510aef177..a56b8ccd7f 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -43,7 +43,7 @@ There are two main ways to use {% data variables.product.prodname_codeql %} anal
 
 ## About {% data variables.product.prodname_codeql %} queries
 
-{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. 更多信息请参阅 GitHub Security Lab 网站上的 [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)。 You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. 更多信息请参阅 {% data variables.product.prodname_codeql %} 网站上的 [{% data variables.product.prodname_codeql %}](https://codeql.github.com/)。 You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
 
 You can run additional queries as part of your code scanning analysis.
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index 1b3d03e411..649eac7ccc 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -18,7 +18,6 @@ topics:
   - Code scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index eafbc64c0b..af256d5d03 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -24,7 +24,7 @@ topics:
   - Python
 shortTitle: Configure code scanning
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
@@ -89,7 +89,7 @@ If you scan pull requests, then the results appear as alerts in a pull request c
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ### Defining the severities causing pull request check failure
 
-By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)."
+By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1  or ghae or ghec %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -351,7 +351,7 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 
 You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 {% if codeql-packs %}
 ### Working with custom configuration files
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 42c5f3df55..6dc4d24289 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -26,7 +26,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 622a6eb37f..6c1d00f0ab 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -16,6 +16,7 @@ topics:
   - Code scanning
 children:
   - /about-code-scanning
+  - /about-code-scanning-alerts
   - /triaging-code-scanning-alerts-in-pull-requests
   - /setting-up-code-scanning-for-a-repository
   - /managing-code-scanning-alerts-for-your-repository
@@ -28,4 +29,4 @@ children:
   - /running-codeql-code-scanning-in-a-container
   - /viewing-code-scanning-logs
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index bc07386975..7747b61120 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -23,62 +23,9 @@ topics:
   - Alerts
   - Repositories
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
-## About alerts from {% data variables.product.prodname_code_scanning %}
-
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
-
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-
-{% data reusables.code-scanning.upload-sarif-alert-limit %}
-
-## About alerts details
-
-Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, security severity,{% endif %} and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
-
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
-
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
-
-When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
-
-### About severity levels
-
-Alert severity levels may be `Error`, `Warning`, or `Note`.
-
-By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### About security severity levels
-
-{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
-
-To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
-
-By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %}
-
-### About labels for alerts that are not found in application code
-
-{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
-
-- **Generated**: Code generated by the build process
-- **Test**: Test code
-- **Library**: Library or third-party code
-- **Documentation**: Documentation
-
-{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
-
-Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code.
-
-![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
-
-On the alert page, you can see that the filepath is marked as library code (`Library` label).
-
-![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
-
 ## Viewing the alerts for a repository
 
 Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
@@ -104,6 +51,8 @@ By default, the code scanning alerts page is filtered to show alerts for the def
 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
    ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
 
+For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
+
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
 
@@ -133,7 +82,7 @@ If you enter multiple filters, the view will show alerts matching _all_ these fi
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 
-You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
+You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% if codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
 
 {% endif %}
 
@@ -177,7 +126,7 @@ You can search the list of alerts. This is useful if there is a large number of
 
 {% endif %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index e367df67c2..fda80ece5a 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -23,7 +23,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index 8bf8ca6ec5..5923e8163b 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -5,9 +5,7 @@ intro: You can add code scanning alerts to issues using task lists. This makes i
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
-  fpt: '*'
-  ghes: '> 3.3'
-  ghae: issue-5036
+  feature: code-scanning-task-lists
 type: how_to
 topics:
   - Advanced Security
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index e1fcdc303e..8abac897b1 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -22,7 +22,6 @@ topics:
   - Repositories
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.beta %}
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index d88ccb0c8f..c60e7ff48f 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -26,7 +26,7 @@ topics:
   - C#
   - Java
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
@@ -192,6 +192,19 @@ If you split your analysis into multiple workflows as described above, we still
 
 If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
 
+### Check which query suites the workflow runs
+
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results. 
+
+You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+{% if codeql-ml-queries %}
+{% note %}
+
+**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+{% endnote %}
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ## Results differ between analysis platforms
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/index.md b/translations/zh-CN/content/code-security/code-scanning/index.md
index 9844b53920..c33b298179 100644
--- a/translations/zh-CN/content/code-security/code-scanning/index.md
+++ b/translations/zh-CN/content/code-security/code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /using-codeql-code-scanning-with-your-existing-ci-system
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
index 0a120a5059..d1f394b381 100644
--- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -19,7 +19,7 @@ topics:
   - Webhooks
   - Integration
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/index.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/index.md
index 6e943484c6..0bf3d38e02 100644
--- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/index.md
+++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/index.md
@@ -22,4 +22,3 @@ children:
   - /sarif-support-for-code-scanning
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
index ab3879863f..c1fc8e6166 100644
--- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -21,7 +21,7 @@ topics:
   - Integration
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
index c0b9b3afea..0beaf40ec0 100644
--- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
+++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -24,7 +24,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index fba109bb62..0ecb4a0c59 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -166,7 +166,7 @@ codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
 | Option | Required | Usage |
 |--------|:--------:|-----|
 | `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. |
-| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/qlpacks/codeql/<language>-queries/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
 | <nobr>`--format`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
 | <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 | <nobr>`--sarif-category`<nobr> | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index f891505bc7..7dca4c5662 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -29,7 +29,6 @@ topics:
   - Java
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
@@ -84,7 +83,7 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-{% data reusables.code-scanning.codeql-query-suites %}
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
 
 要添加一个或多个查询，请将逗号分隔的路径列表传递给 `init` 命令的 `--queries` 标志。 您也可以在配置文件中指定额外查询。
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index 30f6285404..563dd4b85f 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -28,4 +28,3 @@ children:
   - /migrating-from-the-codeql-runner-to-codeql-cli
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index 5f80df6908..17bd093f95 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -50,7 +50,7 @@ These examples assume that the source code has been checked out to the current w
 
 These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH.
 
-In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable.
+In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via `stdin`, or is stored in the `$GITHUB_TOKEN` environment variable.
 
 The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code.
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index 441e52b87a..74078a9855 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -25,7 +25,7 @@ topics:
   - CI
   - SARIF
 ---
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
index e140d7868b..383cabad9c 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -24,7 +24,6 @@ topics:
   - CI
 ---
 
-<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 
 {% data reusables.code-scanning.deprecation-codeql-runner %}
 {% data reusables.code-scanning.beta %}
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
index 92361d61a2..25412c70df 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
@@ -139,3 +139,9 @@ You can view and manage alerts from security features to address dependencies an
 
 {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
+
+{% ifversion ghec %}
+## Further reading
+
+"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/code-security/guides.md b/translations/zh-CN/content/code-security/guides.md
index f1a64f16af..8a73280649 100644
--- a/translations/zh-CN/content/code-security/guides.md
+++ b/translations/zh-CN/content/code-security/guides.md
@@ -30,6 +30,7 @@ includeGuides:
   - /code-security/secret-scanning/secret-scanning-partners
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
   - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
index c117c1bded..69d26b5648 100644
--- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
@@ -15,6 +15,8 @@ topics:
   - Security overview
   - Advanced Security
   - Alerts
+  - Dependabot
+  - Dependencies
   - Organizations
   - Teams
 shortTitle: About security overview
@@ -26,7 +28,7 @@ shortTitle: About security overview
 
 您可以使用安全概述来简要了解组织的安全状态，或识别需要干预的问题仓库。
 
-- 在组织级别，安全概述显示组织拥有的仓库的聚合和仓库特定安全信息。
+- 在组织级别，安全概述显示组织拥有的仓库的聚合和仓库特定安全信息。 You can also filter information per security feature.
 - 在团队级别，安全概述显示团队拥有管理权限的仓库特定安全信息。 For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 - At the repository-level, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features not currently in use.
 
@@ -40,7 +42,7 @@ The application security team at your company can use the security overview for
 
 在安全概述中，您可以查看、排序和筛选警报，以了解组织和特定仓库中的安全风险。 The security summary is highly interactive, allowing you to investigate specific categories of information, based on qualifiers like alert risk level, alert type, and feature enablement. You can also apply multiple filters to focus on narrower areas of interest. 例如，您可以识别具有大量 {% data variables.product.prodname_dependabot_alerts %} 的私有仓库或者没有 {% data variables.product.prodname_code_scanning %} 警报的仓库。 For more information, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
 
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
 
 In the security overview, at both the organization and repository level, there are dedicated views for specific security features, such as secret scanning alerts and code scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository.
 
diff --git a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
index 9ab4dc774c..933ce0941e 100644
--- a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   fpt: '*'
+  ghae: issue-4554
   ghes: '>3.1'
   ghec: '*'
 type: how_to
@@ -99,7 +100,7 @@ Available in the organization-level overview.
 | ------------------------- | ----------------------- |
 | <code>topic:<em>TOPIC-NAME</em></code> | 显示分类为 *TOPIC-NAME* 的仓库。 |
 
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
 
 ## Filter by severity
 
@@ -121,16 +122,16 @@ Available in the code scanning alert views. All code scanning alerts have one of
 
 Available in the secret scanning alert views.
 
-| 限定符                                                                                                                                                                                        | 描述                                                                                                                                                                                                                 |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `secret-type:SERVICE_PROVIDER`                                                                                                                                                             | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners) |
-| `secret-type:CUSTOM-PATTERN`                                                                                                                                                               | Displays alerts for secrets matching the specified custom pattern.                                                                                                                                                 |
-| {% ifversion not fpt %}For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."{% endif %} |                                                                                                                                                                                                                    |
+| 限定符                                                                                                                                                                                        | 描述                                                                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret-type:SERVICE_PROVIDER`                                                                                                                                                             | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners)." |
+| `secret-type:CUSTOM-PATTERN`                                                                                                                                                               | Displays alerts for secrets matching the specified custom pattern.                                                                                                                                                   |
+| {% ifversion not fpt %}For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."{% endif %} |                                                                                                                                                                                                                      |
 
 ## Filter by provider
 
 Available in the secret scanning alert views.
 
-| 限定符                      | 描述                                                                                                                                                                                                                            |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners) |
+| 限定符                      | 描述                                                                                                                                                                                                                              |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} partners](/code-security/secret-scanning/secret-scanning-partners)." |
diff --git a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
index 67c0a90372..ee6d9c8629 100644
--- a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
@@ -5,6 +5,7 @@ permissions: Organization owners and security managers can access the security o
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   fpt: '*'
+  ghae: issue-5503
   ghes: '>3.1'
   ghec: '*'
 type: how_to
@@ -25,8 +26,8 @@ shortTitle: View the security overview
 {% data reusables.organizations.security-overview %}
 1. 要查看有关警报类型的汇总信息，请单击 **Show more（显示更多）**。 ![显示更多按钮](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
-
-{% ifversion ghec or ghes > 3.4 %}
+{% if security-overview-views %}
+1. Alternatively and optionally, use the sidebar on the left to filter information per security feature. On each page, you can use filters that are specific to each feature to fine-tune your search. ![Screenshot of the code scanning-specific page](/assets/images/help/organizations/security-overview-code-scanning-alerts.png)
 
 ## Viewing alerts across your organization
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index e79d34bfac..6336b09402 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -16,7 +16,7 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Use Dependabot with actions
+shortTitle: Use Dependabot with Actions
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
index 4f9737d867..0bbd0b0aa6 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
@@ -27,7 +27,9 @@ shortTitle: 配置选项
 
 {% data variables.product.prodname_dependabot %} 配置文件 *dependabot.yml* 使用 YAML 语法。 如果您是 YAML 的新用户并想要了解更多信息，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。
 
-必须将此文件存储在仓库的 `.github` 目录中。 添加或更新 *dependabot.yml* 文件时，这将触发对版本更新的立即检查。 下次安全警报触发安全更新的拉取请求时将使用所有同时影响安全更新的选项。 For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+必须将此文件存储在仓库的 `.github` 目录中。 添加或更新 *dependabot.yml* 文件时，这将触发对版本更新的立即检查。 For more information and an example, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)."
+
+下次安全警报触发安全更新的拉取请求时将使用所有同时影响安全更新的选项。  For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
 
 *dependabot.yml* 文件有两个必需的顶级密钥：`version` 和 `updates`。 您可以选择性包括一个顶级`注册表`键。 该文件必须以 `version: 2` 开头。
 
@@ -75,7 +77,7 @@ shortTitle: 配置选项
 
 仅对默认分支上有漏洞的包清单提出安全更新。 如果为同一分支设置配置选项（不使用 `target-branch` 时为 true），并为有漏洞的清单指定 `package-ecosystem` 和 `directory`，则安全更新的拉取请求使用相关选项。
 
-一般而言，安全更新会使用影响拉取请求的任何配置选项，例如添加元数据或改变其行为。 For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+一般而言，安全更新会使用影响拉取请求的任何配置选项，例如添加元数据或改变其行为。 有关安全更新的更多信息，请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)”。
 
 {% endnote %}
 
@@ -168,7 +170,7 @@ updates:
 
 {% note %}
 
-**注意**：`时间表` 定义 {% data variables.product.prodname_dependabot %} 尝试更新的时间。 但是，这不是您可收到拉取请求的唯一时间。 更新可基于 `dependabot.yml` 文件的更改、更新失败后清单文件的更改或 {% data variables.product.prodname_dependabot_security_updates %} 触发。 For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+**注意**：`时间表` 定义 {% data variables.product.prodname_dependabot %} 尝试更新的时间。 但是，这不是您可收到拉取请求的唯一时间。 更新可基于 `dependabot.yml` 文件的更改、更新失败后清单文件的更改或 {% data variables.product.prodname_dependabot_security_updates %} 触发。 更多信息请参阅“[{% data variables.product.prodname_dependabot %} 拉取请求的频率](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)”和“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)”。
 
 {% endnote %}
 
@@ -305,7 +307,7 @@ updates:
 
 您可以搜索仓库中是否有 `"@dependabot ignore" in:comments`，以检查仓库是否存储了 `ignore` 首选项。 如果您希望取消忽略以这种方式忽略的依赖项，请重新打开拉取请求。
 
-For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+有关 `@dependabot ignore` 命令的更多信息，请参阅“[管理依赖关系更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。
 
 #### 指定要忽略的依赖项和版本
 
@@ -489,9 +491,9 @@ updates:
 
 ### `registries`
 
-要允许 {% data variables.product.prodname_dependabot %} 在执行版本更新时访问私人包注册表，您必须在相关的 `updates` 配置中包括 `registries` 设置。 您可以通过将 `registrations` 设置为 `"*"` 来允许使用所有定义的注册表。 或者，您可以列出更新可以使用的注册表。 要执行此操作，请使用 _dependabot.yml_ 文件的顶层 `registries` 部分定义的注册表。
+要允许 {% data variables.product.prodname_dependabot %} 在执行版本更新时访问私人包注册表，您必须在相关的 `updates` 配置中包括 `registries` 设置。 您可以通过将 `registrations` 设置为 `"*"` 来允许使用所有定义的注册表。 或者，您可以列出更新可以使用的注册表。 要执行此操作，请使用 _dependabot.yml_ 文件的顶层 `registries` 部分定义的注册表。 For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below.
 
-要允许 {% data variables.product.prodname_dependabot %} 使用 `bundler`、`mix` 和 `pip` 包管理器来更新私人注册表中的依赖项，您可以选择允许外部代码执行。 更多信息请参阅 [`insecure-external-code-execution`](#insecure-external-code-execution)。
+要允许 {% data variables.product.prodname_dependabot %} 使用 `bundler`、`mix` 和 `pip` 包管理器来更新私人注册表中的依赖项，您可以选择允许外部代码执行。 For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
 
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
index 167bb9140f..ed71c81e32 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -52,4 +52,4 @@ Dependabot Preview 已直接植入 {% data variables.product.prodname_dotcom %}
 
 如果使用私人注册表，则必须将现有的 Dependabot Preview 密钥添加到仓库或组织的“ Dependabot 密钥”中。 更多信息请参阅“[管理 Dependabot 的加密密码](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)”。
 
-如果您在迁移方面有任何问题或需要帮助，您可以在 [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) 仓库中查看或打开议题。
+If you have any questions or need help migrating, you can view or open issues in the [`dependabot/dependabot-core`](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index e99fa47420..e0a109f88a 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -38,7 +38,7 @@ redirect_from:
 
 有时，您可能只想更新清单中一个依赖项的版本并生成拉取请求。 但是，如果此直接依赖项的更新版本也更新了依赖项，则拉取请求的更改可能超过您的预期。 每个清单和锁定文件的依赖项审查提供了一种简单的方法来查看更改的内容，以及任何新的依赖项版本是否包含已知的漏洞。
 
-通过检查拉取请求中的依赖项审查并更改被标记为有漏洞的任何依赖项，可以避免将漏洞添加到项目中。 有关依赖项审查工作的更多信息，请参阅“[审查拉取请求中的依赖项更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)”。
+通过检查拉取请求中的依赖项审查并更改被标记为有漏洞的任何依赖项，可以避免将漏洞添加到项目中。 For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
 
 {% data variables.product.prodname_dependabot_alerts %} 将会查找依赖项中存在的漏洞，但避免引入潜在问题比在以后修复它们要好得多。 有关 {% data variables.product.prodname_dependabot_alerts %} 的更多信息，请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 716a544e20..9dfc90486b 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -77,6 +77,9 @@ The recommended formats explicitly define which versions are used for all direct
 | --- | --- | --- | ---|
 | Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
 | `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+{%- if github-actions-in-dependency-graph %}
+| {% data variables.product.prodname_actions %} workflows<sup>[1]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
+{%- endif %}
 {%- ifversion fpt or ghes > 3.2 or ghae %}
 | Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
 {%- elsif ghes = 3.2 %}
@@ -84,18 +87,28 @@ The recommended formats explicitly define which versions are used for all direct
 {%- endif %}
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
-| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* |
+| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
 {%- ifversion fpt or ghes > 3.3 %}
 | Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
 | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
 | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
+{% if github-actions-in-dependency-graph %}
+[1] Please note that {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions)."
+
+[2] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+
+{% else %}
+[1] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+{% endif %}
+
+{% if github-actions-in-dependency-graph %}
 {% note %}
 
-**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+**Note:** {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.
 
 {% endnote %}
-
+{% endif %}
 ## Further reading
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index a508c8e1a8..a8fcc99f86 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -12,7 +12,7 @@ shortTitle: 私有映像注册表
 
 ## 关于私人映像注册表和 {% data variables.product.prodname_codespaces %}
 
-A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more devcontainers. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
+A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more images. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
 
 {% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry.
 
@@ -87,7 +87,7 @@ To access AWS Elastic Container Registry (ECR),  you can provide an AWS access k
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
 *_CONTAINER_REGISTRY_USER = <AWS_ACCESS_KEY_ID>
-*_container_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
+*_CONTAINER_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
 ```
 
 You must also ensure you have the appropriate AWS IAM permissions to perform the credential swap (e.g. `sts:GetServiceBearerToken`) as well as the ECR read operation (either `AmazonEC2ContainerRegistryFullAccess` or `ReadOnlyAccess`).
@@ -97,7 +97,7 @@ Alternatively, if you don't want GitHub to perform the credential swap on your b
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
 *_CONTAINER_REGISTRY_USER = AWS
-*_container_REGISTRY_PASSWORD = <TOKEN>
+*_CONTAINER_REGISTRY_PASSWORD = <TOKEN>
 ```
 
 Since these tokens are short lived and need to be refreshed periodically, we recommend providing an access key ID and secret.
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index d54fdaa121..6f303d1212 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -19,7 +19,7 @@ To learn about pricing for {% data variables.product.prodname_codespaces %}, see
 
 {% data reusables.codespaces.codespaces-billing %}
 
-- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
+- As an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
 
 - For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 56312d6bb9..9a9facfb50 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -41,12 +41,11 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. 向下滚动页面并在 **Secrets（密钥）**下选择 **Codespaces**。 ![侧栏中的代码空间选项](/assets/images/help/codespaces/codespaces-option-secrets.png)
-1. 在页面顶部，单击 **New repository secret（新仓库密钥）**。
-1. 在 **Name（名称）**输入框中键入密码的名称。
-1. 输入密码的值。
-1. 单击 **Add secret（添加密码）**。
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+2. 在页面顶部，单击 **New repository secret（新仓库密钥）**。
+3. 在 **Name（名称）**输入框中键入密码的名称。
+4. 输入密码的值。
+5. 单击 **Add secret（添加密码）**。
 
 ## 为组织添加密钥
 
@@ -56,13 +55,12 @@ topics:
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.sidebar-secret %}
-1. 向下滚动页面并在 **Secrets（密钥）**下选择 **Codespaces**。 ![侧栏中的代码空间选项](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
-1. 在页面顶部，单击 **New organization secret（新组织密钥）**。
-1. 在 **Name（名称）**输入框中键入密码的名称。
-1. 输入密码的 **Value（值）**。
-1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 ![已选定私有仓库的仓库访问列表](/assets/images/help/codespaces/secret-repository-access.png)
-1. 单击 **Add secret（添加密码）**。
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets** then click **{% data variables.product.prodname_codespaces %}**.
+2. 在页面顶部，单击 **New organization secret（新组织密钥）**。
+3. 在 **Name（名称）**输入框中键入密码的名称。
+4. 输入密码的 **Value（值）**。
+5. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 ![已选定私有仓库的仓库访问列表](/assets/images/help/codespaces/secret-repository-access.png)
+6. 单击 **Add secret（添加密码）**。
 
 ## 审查对组织级别密码的访问权限
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 14e98cf19b..e38cc1fe3e 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -47,34 +47,30 @@ If you add an organization-wide policy, you should set it to the largest choice
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.click-codespaces %}
-1. Under "Codespaces", click **Policy**.
-
-   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
-
-1. On the "Codespace policies" page, click **Create Policy**.
-1. Enter a name for your new policy.
-1. Click **Add constraint** and choose **Machine types**.
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policy**.
+2. On the "Codespace policies" page, click **Create Policy**.
+3. Enter a name for your new policy.
+4. Click **Add constraint** and choose **Machine types**.
 
    ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
 
-1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+5. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
 
    ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
 
-1. In the "Change policy target" area, click the dropdown button.
-1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
-1. 如果选择了 **Selected repositories（所选仓库）**：
+6. In the "Change policy target" area, click the dropdown button.
+7. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+8. 如果选择了 **Selected repositories（所选仓库）**：
    1. 单击 {% octicon "gear" aria-label="The settings icon" %}。
 
       ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
 
-   1. Select the repositories you want this policy to apply to.
-   1. At the bottom of the repository list, click **Select repositories**.
+   2. Select the repositories you want this policy to apply to.
+   3. At the bottom of the repository list, click **Select repositories**.
 
       ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
 
-1. 单击 **Save（保存）**。
+9. 单击 **Save（保存）**。
 
 ## Editing a policy
 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
index 013675affa..8d18a87a99 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -33,7 +33,7 @@ hidden: true
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Java、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。
+创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and Yarn. 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。
 
 您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。
 
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
index 41911ce72d..dbc4cf892c 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md
@@ -26,7 +26,7 @@ The name the codespace is also included in many of the log files. For example, i
 
 ### Codespaces IDs
 
-Every codespace also has an ID (identifer). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID.
+Every codespace also has an ID (identifier). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID.
 
 1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace.
 2. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID.
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index e6e64c105e..370066e16b 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -33,7 +33,7 @@ shortTitle: 从您的组织中解除阻止
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.moderation-settings %}
+{% data reusables.organizations.moderation-settings %}, then click **Blocked users**.
 5. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png)
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
index 399d89f9c0..6fdb84d251 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md
@@ -27,6 +27,6 @@ shortTitle: 限制帐户中的交互
 ## 限制用户帐户的交互
 
 {% data reusables.user_settings.access_settings %}
-1. 在在用户设置侧边栏中的“Moderation settings（管理设置）”下，单击 **Interaction limits（交互限制）**。 ![用户设置侧边栏中的"交互限制"选项卡](/assets/images/help/settings/settings-sidebar-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![临时交互限制选项](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index f1e5d5a628..4a9ccd2631 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -33,8 +33,7 @@ shortTitle: 限制组织中的交互
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. 在组织设置侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![组织设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/organizations/org-settings-moderation-settings.png)
-1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![组织设置侧边栏中的"Interaction limits（交互限制）"](/assets/images/help/organizations/org-settings-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![临时交互限制选项](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index 5cb312669a..95d1953596 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -28,8 +28,7 @@ shortTitle: 限制仓库中的交互
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. 在左侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![仓库设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![仓库设置中的交互限制 ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Interaction limits**.
 {% data reusables.community.set-interaction-limit %}
   ![临时交互限制选项](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
new file mode 100644
index 0000000000..5a7f83ee51
--- /dev/null
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
@@ -0,0 +1,641 @@
+---
+title: Common validation errors when creating issue forms
+intro: 'You may see some of these common validation errors when creating, saving, or viewing issue forms.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+---
+
+<!--UI-LINK: We link to individual anchors within this file from the issue template editor when the given YAML error is thrown. Links to and anchors within this file should be preserved or should be updated in github/github if they are changed -->
+{% data reusables.community.issue-forms-beta %}
+
+## Required top level key `name` is missing
+
+The template does not contain a `name` field, which means it is not clear what to call your issue template when giving users a list of options.
+
+### 示例
+
+```yaml
+description: "Thank you for reporting a bug!"
+...
+```
+
+The error can be fixed by adding `name` as a key.
+
+```yaml
+name: "Bug report"
+description: "Thank you for reporting a bug!"
+...
+```
+
+## `key` must be a string
+
+This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported.
+
+### 示例
+
+The `description` below is being parsed as a Boolean, but it should be a string.
+
+```yaml
+name: "Bug report"
+description: true
+...
+```
+
+The error can be fixed by providing a string as the value. Strings may need to be wrapped in double quotes to be successfully parsed. For example, strings that contain `'` must be wrapped in double quotes.
+
+```yaml
+name: "Bug report"
+description: "true"
+...
+```
+
+Empty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string.
+
+```yaml
+name: ""
+description: "File a bug report"
+assignees: "      "
+...
+```
+
+The error can be fixed by correcting the value to be a non-empty string. If the field is not required, you should delete the key-value pair.
+
+```yaml
+name: "Bug Report"
+description: "File a bug report"
+...
+```
+
+## `input` is not a permitted key
+
+An unexpected key was supplied at the top level of the template. For more information about which top-level keys are supported, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax)."
+
+### 示例
+
+```yaml
+name: "Bug report"
+hello: world
+...
+```
+
+The error can be fixed by removing the unexpected keys.
+
+```yaml
+name: "Bug report"
+...
+```
+
+## Forbidden keys
+
+YAML parses certain strings as `Boolean` values. To avoid this, we have explicitly forbidden the usage of the following keys:
+
+`y`, `Y`, `yes`, `Yes`, `YES`, `n`, `N`, `no`, `No`, `NO`, `true`, `True`, `TRUE`, `false`, `False`, `FALSE`, `on`, `On`, `ON`, `off`, `Off`, `OFF`
+
+The error can be fixed by removing the forbidden keys.
+
+## Body must contain at least one non-markdown field
+
+Issue forms must accept user input, which means that at least one of its fields must contain a user input field. A `markdown` element is static text, so a `body` array cannot contain only `markdown` elements.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+```
+
+The error can be fixed by adding non-markdown elements that accept user input.
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+- type: textarea
+  attributes:
+    label: "What's wrong?"
+```
+
+## Body must have unique ids
+
+If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: name
+  attributes:
+    label: Last name
+```
+
+The error can be fixed by changing the `id` for one of these inputs, so that every `input` field has a unique `id` attribute.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: surname
+  attributes:
+    label: Last name
+```
+
+## Body must have unique labels
+
+When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Name
+```
+
+The error can be fixed by changing the `label` attribute for one of the input fields to ensure that each `label` is unique.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Operating System
+```
+
+Input fields can also be differentiated by their `id` attribute. If duplicate `label` attributes are required, you can supply at least one `id` to differentiate two elements with identical labels.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: textarea
+  id: name_2
+  attributes:
+    label: Name
+```
+
+`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+
+
+## Labels are too similar
+
+Similar labels may be processed into identical references. If an `id` attribute is not provided for an `input`, the `label` attribute is used to generate a reference to the `input` field. To do this, we process the `label` by leveraging the Rails [parameterize](https://apidock.com/rails/ActiveSupport/Inflector/parameterize) method. In some cases, two labels that are distinct can be processed into the same parameterized string.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: name
+  attributes:
+    label: Name???????
+```
+
+The error can be fixed by adding at least one differentiating alphanumeric character, `-`, or `_` to one of the clashing labels.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  attributes:
+    label: Your name
+```
+
+The error can also be fixed by giving one of the clashing labels a unique `id`.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: your-name
+  attributes:
+    label: Name???????
+```
+
+## Checkboxes must have unique labels
+
+When a `checkboxes` element is present, each of its nested labels must be unique among its peers, as well as among other input types.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+The error can be fixed by changing the `label` attribute for one of these inputs.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Your name
+```
+
+Alternatively, you can supply an `id` to any clashing top-level elements. Nested checkbox elements do not support the `id` attribute.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+`id` attributes are not visible in the issue body. If you want to distinguish the fields in the resulting issue, you should use distinct `label` attributes.
+
+## Body[i]: required key type is missing
+
+Each body block must contain the key `type`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the zero-indexed index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+The error can be fixed by adding the key `type` with a valid input type as the value. 有关可用的 `body` 输入类型及其语法，请参阅“[{% data variables.product.prodname_dotcom %} 表单架构的语法](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys)”。
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+## Body[i]: `x` is not a valid input type
+
+One of the body blocks contains a type value that is not one of the [permitted types](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys).
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- type: x
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+The error can be fixed by changing `x` to one of the valid types.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+```
+
+## Body[i]: required attribute key `value` is missing
+
+One of the required `value` attributes has not been provided. The error occurs when a block does not have an `attributes` key or does not have a `value` key under the `attributes` key.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+- type: markdown
+```
+
+The error in this example can be fixed by adding `value` as a key under `attributes` in the second list element of `body`.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+    preview_only: false
+- type: markdown
+  attributes:
+    value: "This is working now!"
+```
+
+## Body[i]: label must be a string
+
+Within its `attributes` block, a value has the wrong data type.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+The `label` below is being parsed as a Boolean, but it should be a string.
+
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: true
+```
+
+The error can be fixed by supplying a string value for `label`. If you want to use a `label` value that may be parsed as a Boolean, integer, or decimal, you should wrap the value in quotes. For example, `"true"` or `"1.3"` instead of `true` or `1.3`.
+
+```yaml
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: Environment Details
+```
+
+Empty strings, or strings consisting of only whitespaces, are not permissible when an attribute expects a string. For example, `""` or `"     "` are not allowed.
+
+If the attribute is required, the value must be a non-empty string. If the field is not required, you should delete the key-value pair.
+
+```yaml
+body:
+- type: input
+  attributes:
+    label: "Name"
+```
+
+## Body[i]: `id` can only contain numbers, letters, -, _
+
+`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first name
+  attributes:
+    label: First name
+```
+
+The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first-name
+  attributes:
+    label: First name
+```
+
+## Body[i]: `x` is not a permitted key
+
+An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- type: markdown
+  x: woof
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+The error can be fixed by removing extra keys and only using `type`, `attributes`, and `id`.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+## Body[i]: `label` contains forbidden word
+
+To minimize the risk of private information and credentials being posted publicly in GitHub Issues, some words commonly used by attackers are not permitted in the `label` of input or textarea elements.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Password
+```
+
+The error can be fixed by removing terms like "password" from any `label` fields.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Username
+```
+
+## Body[i]: `x` is not a permitted attribute
+
+An invalid key has been supplied in an `attributes` block.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    x: "a random key!"
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+The error can be fixed by removing extra keys and only using permitted attributes.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+## Body[i]: `options` must be unique
+
+For checkboxes and dropdown input types, the choices defined in the `options` array must be unique.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - ice cream
+      - pie
+```
+
+The error can be fixed by ensuring that no duplicate choices exist in the `options` array.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - pie
+```
+
+## Body[i]: `options` must not include the reserved word, none
+
+"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+      - None
+  validations:
+    required: true
+```
+
+The error can be fixed by removing "None" as an option. If you want a contributor to be able to indicate that they like none of those types of pies, you can additionally remove the `required` validation.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+```
+
+In this example, "None" will be auto-populated as a selectable option.
+
+## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes
+
+There are a number of English words that become processed into Boolean values by the YAML parser unless they are wrapped in quotes. For dropdown `options`, all items must be strings rather than Booleans.
+
+Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
+
+### 示例
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - Yes
+      - No
+      - Maybe
+```
+
+The error can be fixed by wrapping each offending option in quotes, to prevent them from being processed as Boolean values.
+
+```
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - "Yes"
+      - "No"
+      - Maybe
+```
+
+## 延伸阅读
+
+- [YAML](https://yaml.org/)
+- [议题表单的语法](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 20ea522a9d..4b9dc23b81 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -21,5 +21,6 @@ children:
   - /syntax-for-githubs-form-schema
   - /creating-a-pull-request-template-for-your-repository
   - /manually-creating-a-single-issue-template-for-your-repository
+  - /common-validation-errors-when-creating-issue-forms
 ---
 
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
index 5bb76e21e7..3e5e5e1d88 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
@@ -241,7 +241,7 @@ body:
 
 | 键         | 描述                               | 必选 | 类型  | 默认值                                             | 有效值                                             |
 | --------- | -------------------------------- | -- | --- | ----------------------------------------------- | ----------------------------------------------- |
-| `标签`      | 预期用户输入的简短描述，以表单形式显示。             | 可选 | 字符串 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `标签`      | 预期用户输入的简短描述，以表单形式显示。             | 必选 | 字符串 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 | `说明`      | 复选框集的描述，以表单形式显示。 支持 Markdown 格式。 | 可选 | 字符串 | 空字符串                                            | {% octicon "dash" aria-label="The dash icon" %}
 | `options` | 用户可以选择的复选框阵列。 有关语法，请参阅下文。        | 必选 | 数组  | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
index 5d7817d144..f3318e81c7 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -40,7 +40,7 @@ body:
 | `说明`        | 议题表单模板的描述，出现在模板选择器界面中。                 | 必选 | 字符串         |
 | `正文`        | 表单中输入类型的定义。                            | 必选 | 数组          |
 | `assignees` | 将自动分配给使用此模板创建的议题的人员。                   | 可选 | 阵列或逗号分界的字符串 |
-| `labels`    | 将自动添加到此模板创建的议题的标签。                     | 可选 | 字符串         |
+| `labels`    | 将自动添加到此模板创建的议题的标签。                     | 可选 | 阵列或逗号分界的字符串 |
 | `title`     | 在议题提交表单中预填的默认标题。                       | 可选 | 字符串         |
 
 有关可用的 `body` 输入类型及其语法，请参阅“[{% data variables.product.prodname_dotcom %} 表单架构的语法](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema)”。
@@ -165,3 +165,4 @@ body:
 ## 延伸阅读
 
 - [YAML](https://yaml.org/)
+- [Common validation errors when creating issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms)
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 27e2822897..fc4e29ad61 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -99,7 +99,7 @@ shortTitle: 应用程序创建查询参数
 | [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | 授予对[代码扫描 API](/rest/reference/code-scanning/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
 | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                       |
 | [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                             | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                    |
-| [`状态`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                             | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                       |
+| [`状态`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                             | 授予对[状态 API](/rest/reference/commits#commit-statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                              |
 | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 | `vulnerability_alerts`                                                                                                           | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)”。 可以是以下项之一：`none` 或 `read`。{% endif %}
 | `关注`                                                                                                                             | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                                                       |
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index f3f0f6d45e..162c197d63 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -449,8 +449,8 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 {% ifversion fpt or ghec %}
 #### 组织团队同步
 
-* [列出团队的 idp 组](/rest/reference/teams#list-idp-groups-for-a-team)
-* [创建或更新 idp 组连接](/rest/reference/teams#create-or-update-idp-group-connections)
+* [List IdP groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
+* [Create or update IdP group connections](/rest/reference/teams#create-or-update-idp-group-connections)
 * [列出组织的 IdP 组](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
index 632fdeb9aa..aabf472d4c 100644
--- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -54,7 +54,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 ## 步骤 1. 启动新的 Sme 通道
 
-为了帮助 GitHub 将 web 挂钩发送到您的本地计算机而不将其暴露在互联网上，您可以使用一个名为 Smee 的工具。 首先，转到 https://smee.io，然后单击 **Start a new channel（启动新通道）**。 如果您已经习惯使用将本地计算机暴露到互联网上的其他工具，例如 [ngrok](https://dashboard.ngrok.com/get-started) 或 [localtunnel](https://localtunnel.github.io/www/)，请随意使用。
+为了帮助 GitHub 将 web 挂钩发送到您的本地计算机而不将其暴露在互联网上，您可以使用一个名为 Smee 的工具。 首先，转到 https://smee.io，然后单击 **Start a new channel（启动新通道）**。 If you're already comfortable with other tools that expose your local machine to the internet like [`ngrok`](https://dashboard.ngrok.com/get-started) or [`localtunnel`](https://localtunnel.github.io/www/), feel free to use those.
 
 ![Smee 新通道按钮](/assets/images/smee-new-channel.png)
 
@@ -91,7 +91,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 `smee --url <unique_channel>` 命令指示 Smee 将 Smee 通道接收的所有 web 挂钩事件转发到计算机上运行的 Smee 客户端。 `--path /event_handler` 选项将事件转发到 `/event_handler` 路由，我们将在[后面的章节](#step-5-review-the-github-app-template-code)中介绍。 `--port 3000` 选项指定端口 3000，这是服务器将侦听的端口。 使用 Smee，您的计算机不需要向公共互联网开放即可从 GitHub 接收 web 挂钩。 您也可以在浏览器中打开 Smee URL 来检查 web 挂钩有效负载。
 
-我们建议您在完成本指南其余步骤时保持此终端窗口打开并保持 Smee 连接。 尽管您_可以_断开连接后重新连接 Smee 客户端而不会丢失唯一域（与 ngrok 不同），但您可能会发现，保持连接时在其他终端窗口中执行其他命令行任务更容易。
+我们建议您在完成本指南其余步骤时保持此终端窗口打开并保持 Smee 连接。 Although you _can_ disconnect and reconnect the Smee client without losing your unique domain (unlike `ngrok`), you may find it easier to leave it connected and do other command-line tasks in a different Terminal window.
 
 ## 步骤 2. 注册新的 GitHub 应用程序
 
@@ -131,7 +131,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 创建应用程序后，您将被带回[应用程序设置页面](https://github.com/settings/apps)。 您还有两件事要做：
 
-* **为应用程序生成私钥。**这是以后验证应用程序所必需的。 向下滚动页面，然后单击 **Generate a private key（生成私钥）**。 将生成的 PEM 文件（称为 _`app-name`_-_`date`_-private-key.pem 等）保存在可以再次找到的目录中。
+* **为应用程序生成私钥。**这是以后验证应用程序所必需的。 向下滚动页面，然后单击 **Generate a private key（生成私钥）**。 Save the resulting `PEM` file (called something like  _`app-name`_-_`date`_-`private-key.pem`) in a directory where you can find it again.
 
     ![私钥生成对话框](/assets/images/private_key.png)
 
diff --git a/translations/zh-CN/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
index ae172d8eed..1fe460024b 100644
--- a/translations/zh-CN/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
+++ b/translations/zh-CN/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
@@ -157,7 +157,7 @@ end
 
 此代码使用 [create_check_run 方法](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run)调用“[创建检查运行](/rest/reference/checks#create-a-check-run)”端点。
 
-要创建检查运行，只有两个输入参数是必需的：`name` 和 `head_sha`。 在本快速入门中的稍后部分，我们将使用 [Rubocop](https://rubocop.readthedocs.io/en/latest/) 来实现 CI 测试，这就是在此处使用名称 "Octo Rubocop" 的原因，但是您可以为检查运行选择任何想用的名称。
+要创建检查运行，只有两个输入参数是必需的：`name` 和 `head_sha`。 We will use [RuboCop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo RuboCop" is used here, but you can choose any name you'd like for the check run.
 
 您现在仅提供必需的参数以使基本功能正常工作，但是稍后您将在收集有关检查运行的更多信息时更新检查运行。 默认情况下，GitHub 将 `status` 设置为 `queued`。
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index ca9d6d5132..bb233098eb 100644
--- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -29,7 +29,7 @@ Insights 页面显示选定时段的以下性能指标：
 
 * **Subscription value（订阅价值）：**订阅的可能总收入（美元）。 此值表示在没有计划或免费试用被取消并且所有信用交易都成功的情况下的可能收入。 订阅价值包括计划在选定时段内的全部价值，从免费试用开始计算，即使在该时段内没有任何财务交易。 订阅价值还包括选定时段内升级计划的全部价值，但不包括按比例分配的金额。 要查看和下载单个交易，请参阅“[GitHub Marketplace 交易](/marketplace/github-marketplace-transactions/)”。
 * **Visitors（访客数）：**查看过 GitHub 应用程序上架页面的人数。 此数字包括已登录和已注销的访客。
-* **Pageviews（网页浏览量）：**GitHub 应用程序上架页面获得的浏览次数。 单个访客可以产生多个网页浏览量。
+* **Pageviews（网页浏览量）：**GitHub 应用程序上架页面获得的浏览次数。 A single visitor can generate more than one page view.
 
 {% note %}
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
index 076b6d74cd..022729dab9 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
@@ -19,7 +19,7 @@ shortTitle: 提交您的列表
 
   ![Marketplace 上架信息草稿的选项概述](/assets/images/marketplace/edit-marketplace-listing-overview.png)
 
-2. 要提交已完成的应用程序上架信息，请单击 **Request publish（请求发布）**。
+2. To submit your completed app listing, click **Request publish**.
 
   !["将应用程序发布到 Marketplace"检查列表，底部有提交按钮](/assets/images/marketplace/publish-your-app-checklist-and-submission.png)
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
index 54fb39ac9f..afde8edef1 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
@@ -58,7 +58,7 @@ When a customer purchases your app, you must send the customer through the OAuth
 
 * If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)."
 
-For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize.
+For either type of app, the first step is to redirect the customer to [https://github.com/login/oauth/authorize](https://github.com/login/oauth/authorize).
 
 After the customer completes the authorization, your app receives an OAuth access token for the customer. You'll need this token for the next step.
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index dfaa999146..1bdadd77a5 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -50,7 +50,7 @@ topics:
 
 您可以使用升级 URL 将用户从应用程序的 UI 重定向到 GitHub 上的升级页面：
 
-```
+```text
 https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
 ```
 
diff --git a/translations/zh-CN/content/developers/overview/about-githubs-apis.md b/translations/zh-CN/content/developers/overview/about-githubs-apis.md
index 33bfa287d7..f5a0ccfc8d 100644
--- a/translations/zh-CN/content/developers/overview/about-githubs-apis.md
+++ b/translations/zh-CN/content/developers/overview/about-githubs-apis.md
@@ -3,6 +3,8 @@ title: 关于 GitHub 的 API
 intro: '了解 {% data variables.product.prodname_dotcom %} 的 API 以扩展和自定义您的 {% data variables.product.prodname_dotcom %} 体验。'
 redirect_from:
   - /v3/versions
+  - /articles/getting-started-with-the-api
+  - /github/extending-github/getting-started-with-the-api
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
index 569c67a9fc..ca2eec5233 100644
--- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
+++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
@@ -34,11 +34,11 @@ topics:
 #### 设置
 
 1. 在本地开启代理转发。 更多信息请参阅[我们的 SSH 代理转发指南][ssh-agent-forwarding]。
-2. 将部署脚本设置为使用代理转发。 例如，在 bash 脚本中，启用代理转发如下所示：`ssh -A serverA 'bash -s' < deploy.sh`
+2. 将部署脚本设置为使用代理转发。 For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh`
 
 ## 使用 OAuth 令牌进行 HTTPS 克隆
 
-如果不想使用 SSH 密钥，您可以使用 [HTTPS 结合 OAuth 令牌][git-automation]。
+If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
 
 #### 优点
 
@@ -57,7 +57,7 @@ topics:
 
 #### 设置
 
-请参阅[使用令牌的 Git 自动化指南][git-automation]。
+See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
 ## 部署密钥
 
@@ -78,7 +78,7 @@ topics:
 
 #### 设置
 
-1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并记住保存生成的公共/私有 RSA 密钥对的位置。
+1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair key pair.
 2. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your profile（您的个人资料）**。 ![个人资料导航](/assets/images/profile-page.png)
 3. 在个人资料页面上，单击 **Repositories（仓库）**，然后单击仓库的名称。 ![仓库链接](/assets/images/repos.png)
 4. 在仓库中，单击 **Settings（设置）**。 ![仓库设置](/assets/images/repo-settings.png)
@@ -182,10 +182,8 @@ $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.c
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
+[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
-[git-automation]: /articles/git-automation-with-oauth-tokens
-[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
-
diff --git a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
index 152a12a255..ab6e871ea0 100644
--- a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
@@ -79,7 +79,7 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 
 ### 您必须使用 SSH URL 检出代码
 
-SSH 转发仅适用于 SSH URL，而不是 HTTP(s) URL。 检查服务器上的 *.git/config* 文件，并确保 URL 是 SSH 样式的 URL，如下所示：
+SSH 转发仅适用于 SSH URL，而不是 HTTP(s) URL。 检查服务器上的 `.git/config` 文件，并确保 URL 是 SSH 样式的 URL，如下所示：
 
 ```shell
 [remote "origin"]
@@ -107,7 +107,7 @@ $ exit
 # Returns to your local command prompt
 ```
 
-在上面的示例中，先加载 *~/.ssh/config* 文件，然后读取 */etc/ssh_config* 文件。  通过运行以下命令，我们可以检查该文件以查看它是否覆盖了我们的选项：
+在上面的示例中，先加载 `~/.ssh/config` 文件，然后读取 `/etc/ssh_config` 文件。  通过运行以下命令，我们可以检查该文件以查看它是否覆盖了我们的选项：
 
 ```shell
 $ cat /etc/ssh_config
@@ -117,7 +117,7 @@ $ cat /etc/ssh_config
 >   ForwardAgent no
 ```
 
-在此示例中，我们的 */etc/ssh_config* 文件特别表示 `ForwardAgent no`，这是一种阻止代理转发的方式。 从文件中删除此行应该会使代理转发再次起作用。
+在此示例中，我们的 `/etc/ssh_config` 文件特别表示 `ForwardAgent no`，这是一种阻止代理转发的方式。 从文件中删除此行应该会使代理转发再次起作用。
 
 ### 您的服务器必须允许入站连接上的 SSH 代理转发
 
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
index b94e0c034d..5938246f6a 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
@@ -22,9 +22,9 @@ topics:
 
 ## 向互联网显示本地主机
 
-在本教程中，我们将使用本地服务器接收来自 {% data variables.product.prodname_dotcom %} 的消息。 因此，首先，我们需要将我们的本地发展环境显示给互联网。 我们将使用 ngrok 实现此目的。 所有主要操作系统均可免费使用 ngrok。 更多信息请参阅 [ngrok 下载页面](https://ngrok.com/download)。
+在本教程中，我们将使用本地服务器接收来自 {% data variables.product.prodname_dotcom %} 的消息。 因此，首先，我们需要将我们的本地发展环境显示给互联网。 我们将使用 ngrok 实现此目的。 所有主要操作系统均可免费使用 ngrok。 For more information, see [the `ngrok` download page](https://ngrok.com/download).
 
-在安装 ngrok 后，您可以在命令行上运行 `./ngrok http 4567` 以暴露本地主机。 4567 是我们服务器侦听消息的端口号。 您应该会看到如下所示的行：
+After installing `ngrok`, you can expose your localhost by running `./ngrok http 4567` on the command line. 4567 是我们服务器侦听消息的端口号。 您应该会看到如下所示的行：
 
 ```shell
 $ Forwarding    http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
index 0cd3813489..e70233b26e 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
@@ -9,5 +9,6 @@ children:
   - /managing-discussions-in-your-repository
   - /managing-categories-for-discussions-in-your-repository
   - /moderating-discussions
+  - /viewing-insights-for-your-discussions
 ---
 
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
new file mode 100644
index 0000000000..91a0cb9e79
--- /dev/null
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -0,0 +1,34 @@
+---
+title: Viewing insights for your discussions
+intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.'
+permissions: Repository administrators and people with maintain access to a repository can view the discussions insights dashboard.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Discussions
+shortTitle: View discussions insights
+---
+
+## About the discussions insights dashboard
+
+You can use discussions insights to help understand the contribution activity, page views, and growth of your repository's discussions community.
+- **Contribution activity** shows the count of total contributions to discussions, issues, and pull requests.
+- **Discussions page views** shows the total page views for discussions, segmented by logged in versus anonymous viewers.
+- **Discussions daily contributors** shows the daily count of unique users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
+- **Discussions new contributors** shows the daily count of unique new users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
+
+![Screenshot of the discussions dashboard](/assets/images/help/discussions/discussions-dashboard.png)
+
+{% tip %}
+
+**Tip:** To view the exact data for a time period, hover over that time period in the graph.
+
+{% endtip %}
+
+## Viewing discussions insights
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+3. 在左侧栏中，单击 **Community（社区）**。 ![Screenshot of the "Community" tab in left sidebar](/assets/images/help/graphs/graphs-sidebar-community-tab.png)
+1. Optionally, in the upper-right corner of the page, select the **Period** dropdown menu and click the time period for which you want to view data: **30 days**, **3 months**, or **1 year**. ![Screenshot of the date range selector for discussions insights](/assets/images/help/discussions/discussions-dashboard-date-selctor.png)
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
new file mode 100644
index 0000000000..fef163b17b
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
@@ -0,0 +1,35 @@
+---
+title: About GitHub Marketplace
+intro: '{% data variables.product.prodname_marketplace %} contains tools that add functionality and improve your workflow.'
+redirect_from:
+  - /articles/about-github-marketplace
+  - /github/customizing-your-github-workflow/about-github-marketplace
+  - /github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace  
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
+
+If you purchase a paid tool, you'll pay for your tool subscription with the same billing information you use to pay for your {% data variables.product.product_name %} subscription, and receive one bill on your regular billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+You may also have the option to select a free 14-day trial on some tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+## Finding tools on {% data variables.product.prodname_marketplace %}
+
+You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)."
+
+{% data reusables.actions.actions-not-verified %}
+
+Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a marketplace badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About GitHub Marketplace](/developers/github-marketplace/about-github-marketplace)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)."
+
+## Building and listing a tool on {% data variables.product.prodname_marketplace %}
+
+For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)."
+
+## Further reading
+
+- "[Purchasing and installing apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)"
+- "[Managing billing for {% data variables.product.prodname_marketplace %} apps](/articles/managing-billing-for-github-marketplace-apps)"
+- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)"
+- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)"
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
new file mode 100644
index 0000000000..24a8126f0b
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -0,0 +1,43 @@
+---
+title: 关于集成
+intro: '集成是连接 {% data variables.product.product_name %} 服务以完善和扩展工作流程的工具与服务。'
+redirect_from:
+  - /articles/about-integrations
+  - /github/customizing-your-github-workflow/about-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/about-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+您可以在您的个人帐户或拥有的组织中安装集成， 也可从您具有管理员权限或者您的组织所拥有的特定仓库中的第三方安装 {% data variables.product.prodname_github_apps %}。
+
+## {% data variables.product.prodname_github_apps %} 与 {% data variables.product.prodname_oauth_apps %} 之间的差异
+
+集成可以是 {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}，或任何使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 或 web 挂钩的工具。
+
+{% data variables.product.prodname_github_apps %} 可提供细致的权限，申请只访问应用程序需要的内容。 {% data variables.product.prodname_github_apps %} 还提供特定的用户级权限，当应用程序安装或者集成者更改应用程序请求的权限时，每个用户都必须个别授权。
+
+更多信息请参阅：
+- "[{% data variables.product.prodname_github_apps %} 与 {% data variables.product.prodname_oauth_apps %} 之间的差异](/apps/differences-between-apps/)"
+- "[关于应用程序](/apps/about-apps/)"
+- “[用户级权限](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)”
+- "[授权 {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Authorizing {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[审查授权的集成](/articles/reviewing-your-authorized-integrations/)"
+
+如果集成者或应用程序创建者使用 {% data variables.product.prodname_github_app %} 清单流程创建了应用程序，您可以安装预配置的 {% data variables.product.prodname_github_app %}。 有关如何以自动化配置运行 {% data variables.product.prodname_github_app %} 的信息，请联系集成者或应用程序创建者。
+
+如果使用 Probot 构建应用程序，您可以通过简化的配置创建 {% data variables.product.prodname_github_app %}。 更多信息请参阅 [Probot 文档](https://probot.github.io/docs/)站点。
+
+## 发现 {% data variables.product.prodname_marketplace %} 中的集成
+
+您可以在 {% data variables.product.prodname_marketplace %} 中查找要安装的集成或发布您自己的集成。
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 包含 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %}。 有关查找集成或创建您自己的集成的更多信息，请参阅“[关于 {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)”。
+
+## 直接从集成者购买的集成
+
+您也可以直接从集成者购买一些集成。 作为组织成员，如果您发现喜欢使用的 {% data variables.product.prodname_github_app %}，可以申请组织批准并为组织安装该应用程序。
+
+如果您对其中安装应用程序的所有组织拥有的仓库具有管理员权限，可以使用仓库级权限安装 {% data variables.product.prodname_github_apps %}，而无需要求组织所有者批准该应用程序。 当集成者更改应用程序的权限时，如果权限只适用于仓库，则组织所有者以及对安装应用程序的仓库具有管理员权限的人员可以审查和接受新权限。
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
new file mode 100644
index 0000000000..831df21b90
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
@@ -0,0 +1,32 @@
+---
+title: 关于 web 挂钩
+redirect_from:
+  - /post-receive-hooks
+  - /articles/post-receive-hooks
+  - /articles/creating-webhooks
+  - /articles/about-webhooks
+  - /github/extending-github/about-webhooks
+intro: Web 挂钩是一种通知方式，只要仓库或组织上发生特定操作，就会发送通知到外部 web 服务器。
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% tip %}
+
+**提示：** {% data reusables.organizations.owners-and-admins-can %} 为组织管理 web 挂钩。 {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+只要在仓库或组织上执行特定的操作，就可触发 web 挂钩。 例如，您可以配置 web 挂钩在以下情况下执行：
+
+* 推送到仓库
+* 打开拉取请求
+* 构建 {% data variables.product.prodname_pages %} 网站
+* 团队新增成员
+
+使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 可以让这些 web 挂钩更新外部议题跟踪器、触发 CI 构建、更新备份镜像，甚至部署到生产服务器。
+
+要设置新的 web 挂钩，您需要访问外部服务器并熟悉所涉及的技术程序。 有关构建 web 挂钩的帮助，包括可以关联的完整操作列表，请参阅“[web 挂钩](/webhooks)”。
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
new file mode 100644
index 0000000000..5e46b9bea5
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -0,0 +1,55 @@
+---
+title: GitHub 扩展和集成
+intro: '通过 {% data variables.product.product_name %} 扩展可在第三方应用程序中无缝使用 {% data variables.product.product_name %} 仓库。'
+redirect_from:
+  - /articles/about-github-extensions-for-third-party-applications
+  - /articles/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: 扩展和集成
+---
+
+## 编辑器工具
+
+您可以在第三方编辑器工具中连接到 {% data variables.product.product_name %} 仓库，例如 Atom、Unity 和 Visual Studio 等工具。
+
+### {% data variables.product.product_name %} for Atom
+
+使用 {% data variables.product.product_name %} for Atom 扩展，您可以从 Atom 编辑器中提交、推送、拉取和解决合并冲突等。 更多信息请参阅官方 [{% data variables.product.product_name %} for Atom 站点](https://github.atom.io/)。
+
+### {% data variables.product.product_name %} for Unity
+
+使用 {% data variables.product.product_name %} for Unity 编辑器扩展，您可以在开源游戏开发平台 Unity 上进行开发，在 {% data variables.product.product_name %} 查看您的工作。 更多信息请参阅官方 Unity 编辑器扩展[站点](https://unity.github.com/)或[文档](https://github.com/github-for-unity/Unity/tree/master/docs)。
+
+### {% data variables.product.product_name %} for Visual Studio
+
+使用 {% data variables.product.product_name %} for Visual Studio 扩展，您可以 Visual Studio 中处理 {% data variables.product.product_name %} 仓库。 更多信息请参阅官方 Visual Studio 扩展[站点](https://visualstudio.github.com/)或[文档](https://github.com/github/VisualStudio/tree/master/docs)。
+
+### {% data variables.product.prodname_dotcom %} for Visual Studio Code
+
+使用 {% data variables.product.prodname_dotcom %} for Visual Studio Code 扩展，您可以在 Visual Studio Code 中审查和管理 {% data variables.product.product_name %} 拉取请求。 更多信息请参阅官方 Visual Studio Code 扩展[站点](https://vscode.github.com/)或[文档](https://github.com/Microsoft/vscode-pull-request-github)。
+
+## 项目管理工具
+
+您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方项目管理工具（如 Jira）集成。
+
+### Jira Cloud 与 {% data variables.product.product_name %}.com 集成
+
+您可以将 Jira Cloud 与个人或组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。 更多信息请访问 Marketplace 中的 [Jira 集成应用程序](https://github.com/marketplace/jira-software-github)。
+
+## 团队通信工具
+
+您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方团队通信工具（如 Slack 或 Microsoft Teams）集成。
+
+### Slack 与 {% data variables.product.product_name %} 集成
+
+您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、发布、部署审查和部署状态的实时更新。 您还可以执行关闭或打开议题等活动，并在不离开 Slack 的情况下提供丰富的议题和拉取请求参考。
+
+The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). 更多信息请访问 Marketplace 中的 [Slack 集成应用程序](https://github.com/marketplace/slack-github)。
+
+### Microsoft Teams 与 {% data variables.product.product_name %} 集成
+
+您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、部署审查和部署状态的实时更新。 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 Microsoft Teams。 更多信息请访问 Microsoft AppSource 中的 [Microsoft Teams 集成应用程序](https://appsource.microsoft.com/en-us/product/office/WA200002077)。
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
new file mode 100644
index 0000000000..651e5782f0
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
@@ -0,0 +1,18 @@
+---
+title: 探索集成
+intro: '您可以使用 {% data variables.product.product_name %} 社区构建的工具和服务，自定义和扩展您的 {% data variables.product.product_name %} 工作流程。'
+redirect_from:
+  - /articles/exploring-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-integrations
+  - /about-webhooks
+  - /about-github-marketplace
+  - /github-extensions-and-integrations
+---
+
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md
new file mode 100644
index 0000000000..1131407cca
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md
@@ -0,0 +1,17 @@
+---
+title: 自定义 GitHub 工作流程
+intro: 'Learn how you can customize your {% data variables.product.prodname_dotcom %} workflow with extensions, integrations, {% data variables.product.prodname_marketplace %}, and webhooks.'
+redirect_from:
+  - /categories/customizing-your-github-workflow
+  - /github/customizing-your-github-workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: '*'
+  ghes: '*'
+children:
+  - /exploring-integrations
+  - /purchasing-and-installing-apps-in-github-marketplace
+shortTitle: 自定义工作流程
+---
+
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
new file mode 100644
index 0000000000..021621c2f2
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
@@ -0,0 +1,15 @@
+---
+title: 在 GitHub Marketplace 中购买并安装应用程序
+intro: '{% data variables.product.prodname_marketplace %} 包含的应用程序中有免费和付费定价计划。 找到想用于个人帐户或组织的付费应用程序后，您可以使用现有的计费信息购买并安装该应用程序。'
+redirect_from:
+  - /articles/purchasing-and-installing-apps-in-github-marketplace
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /installing-an-app-in-your-personal-account
+  - /installing-an-app-in-your-organization
+shortTitle: 安装 Marketplace app
+---
+
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
new file mode 100644
index 0000000000..2845d303d8
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: 在组织中安装应用程序
+intro: '您可以从 {% data variables.product.prodname_marketplace %} 安装要在组织中使用的应用程序。'
+redirect_from:
+  - /articles/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: 安装应用组织
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+如果选择付费计划，则要使用组织现有的支付方式，在组织的当前结算日期支付应用程序订阅。
+
+{% data reusables.marketplace.free-trials %}
+
+## 在组织中安装 {% data variables.product.prodname_github_app %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 如果应用程序需要访问仓库，请决定允许应用程序访问您的所有仓库还是某些仓库，然后选择 **All repositories（所有仓库）**或 **Only select repositories（仅所选仓库）**。 ![用于在所有仓库或某些仓库上安装应用程序的选项单选按钮](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## 在组织中安装 {% data variables.product.prodname_oauth_app %}
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-org %}
+{% data reusables.marketplace.add-payment-method-org %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 检查有关应用程序对您的个人帐户、组织和数据访问权限的信息，然后单击 **Authorize application（授权应用程序）**。
+
+## 延伸阅读
+
+- "[更新组织的支付方式](/articles/updating-your-organization-s-payment-method)"
+- "[在个人帐户中安装应用程序](/articles/installing-an-app-in-your-personal-account)"
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
new file mode 100644
index 0000000000..50832fe2a0
--- /dev/null
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -0,0 +1,49 @@
+---
+title: 在个人帐户中安装应用程序
+intro: '您可以从 {% data variables.product.prodname_marketplace %} 安装要在个人帐户中使用的应用程序。'
+redirect_from:
+  - /articles/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: 安装应用程序用户帐户
+---
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+如果选择付费计划，则要使用组织现有的支付方式，在个人帐户的当前结算日期支付应用程序订阅。
+
+{% data reusables.marketplace.free-trials %}
+
+## 在个人帐户中安装 {% data variables.product.prodname_github_app %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 决定允许应用程序访问您的所有仓库还是某些仓库，然后选择 **All repositories（所有仓库）**或 **Only select repositories（仅所选仓库）**。 ![用于在所有仓库或某些仓库上安装应用程序的选项单选按钮](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png)
+{% data reusables.marketplace.select-installation-repos %}
+{% data reusables.marketplace.review-app-perms-install %}
+
+## 在个人帐户中安装 {% data variables.product.prodname_oauth_app %}
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %}
+{% data reusables.marketplace.browse-to-app %}
+{% data reusables.marketplace.choose-plan %}
+{% data reusables.marketplace.install-buy %}
+{% data reusables.marketplace.confirm-install-account-personal %}
+{% data reusables.marketplace.add-payment-method-personal %}
+{% data reusables.marketplace.complete-order-begin-installation %}
+8. 检查有关应用程序对您的个人帐户和数据访问权限的信息，然后单击 **Authorize application（授权应用程序）**。
+
+## 延伸阅读
+
+- "[更新个人帐户的支付方式](/articles/updating-your-personal-account-s-payment-method)"
+- "[在组织中安装应用程序](/articles/installing-an-app-in-your-organization)"
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index a2b7a4076c..4ffafad222 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -49,7 +49,7 @@ shortTitle: 关联文本编辑器
 ## 使用 TextMate 作为编辑器
 
 1. 安装 [TextMate](https://macromates.com/)。
-2. 安装 TextMate 的 `mate` shell 实用程序。 更多信息请参阅 TextMate 文档中的“[mate 和 rmate](https://macromates.com/blog/2011/mate-and-rmate/)”。
+2. 安装 TextMate 的 `mate` shell 实用程序。 For more information, see "[`mate` and `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
 {% data reusables.command_line.open_the_multi_os_terminal %}
 4. 输入此命令：
   ```shell
diff --git a/translations/zh-CN/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md b/translations/zh-CN/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
index 7f93ffc676..5a4efc013a 100644
--- a/translations/zh-CN/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
+++ b/translations/zh-CN/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
@@ -12,15 +12,15 @@ versions:
 shortTitle: GitHub 支持的属性
 ---
 
-## 可执行文件 (svn:executable)
+## Executable files (`svn:executable`)
 
 我们通过在将文件模式添加到 Git 仓库之前直接进行更新来转换 `svn:executable` 属性。
 
-## MIME 类型 (svn:mime-type)
+## MIME types (`svn:mime-type`)
 
 {% data variables.product.product_name %} 内部跟踪文件的 mime 类型和添加它们的提交。
 
-## 忽略未版本化的项目 (svn:ignore)
+## Ignoring unversioned items (`svn:ignore`)
 
 如果您已设置要在 Subversion 中忽略的文件和目录，{% data variables.product.product_name %} 将在内部跟踪它们。 Subversion 客户端忽略的文件与 *.gitignore* 文件中的条目完全不同。
 
diff --git a/translations/zh-CN/content/get-started/index.md b/translations/zh-CN/content/get-started/index.md
index 918268f517..3ea2dcc101 100644
--- a/translations/zh-CN/content/get-started/index.md
+++ b/translations/zh-CN/content/get-started/index.md
@@ -62,6 +62,7 @@ children:
   - /exploring-projects-on-github
   - /getting-started-with-git
   - /using-git
+  - /customizing-your-github-workflow
   - /privacy-on-github
 ---
 
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index d922505b6e..716f08bbeb 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -12,7 +12,7 @@ shortTitle: GitHub AE trial
 
 You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
-- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
+- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the deployment of {% data variables.product.prodname_ghe_managed %}.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
 ## 设置 {% data variables.product.prodname_ghe_managed %} 的试用版
@@ -39,24 +39,24 @@ The email address you entered above will receive instructions on how to access y
 
 {% note %}
 
-**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} instance are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
+**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} deployment are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
 
 {% endnote %}
 
 ## Navigating to your enterprise
 
-You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
+You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} deployment. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} deployments in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
 1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
 ## 后续步骤
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)。”
+Once your deployment has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)。”
 
 ## 结束试用
 
-You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
+You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the deployment is automatically deleted.
 
 如果需要更多时间来评估 {% data variables.product.prodname_ghe_managed %}，请联系 {% data variables.contact.contact_enterprise_sales %} 申请延期。
 
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 5953009d94..5ec162d528 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -25,11 +25,9 @@ shortTitle: Enterprise Cloud 试用版
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
-{% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
 
-{% data reusables.enterprise-accounts.emu-short-summary %}
-
-{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+试用版也可用于 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-server)”。
 
 {% data reusables.products.which-product-to-use %}
 
@@ -39,7 +37,11 @@ You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe
 
 试用版包括 50 个席位。 如果需要更多席位来评估 {% data variables.product.prodname_ghe_cloud %}，请联系 {% data variables.contact.contact_enterprise_sales %}。 在试用结束时，您可以选择不同数量的席位。
 
-试用版也可用于 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-server)”。
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
 
 ## 设置 {% data variables.product.prodname_ghe_cloud %} 的试用版
 
@@ -60,11 +62,13 @@ Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be
 
 ## 结束试用
 
-在试用期间，您可以随时购买 {% data variables.product.prodname_enterprise %} 或降级到 {% data variables.product.prodname_team %}。
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
 
-如果在试用期结束前没有购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} ， 您的组织将会降级到 {% data variables.product.prodname_free_team %}，不能使用只包含在付费产品中的任何高级工具和功能，包括从那些私有仓库发布的 {% data variables.product.prodname_pages %} 站点。 如果您不打算升级，为避免失去高级功能的使用权限，请在试用结束前将仓库设为公共。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}.
 
-对于组织来说，降级到 {% data variables.product.prodname_free_team %} 还会禁用试用期间配置的任何 SAML 设置。 购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} 后，您的 SAML 设置将再次启用，以便您组织中的用户进行身份验证。
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md b/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
index d9e79d6f23..4732215303 100644
--- a/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
@@ -53,7 +53,7 @@ versions:
 
 1. 新增指向我们感兴趣的单独项目的远程 URL。
   ```shell
-  $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
+  $ git remote add -f spoon-knife https://github.com/octocat/Spoon-Knife.git
   > Updating spoon-knife
   > warning: no common commits
   > remote: Counting objects: 1732, done.
@@ -61,7 +61,7 @@ versions:
   > remote: Total 1732 (delta 1086), reused 1558 (delta 967)
   > Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done.
   > Resolving deltas: 100% (1086/1086), done.
-  > From git://github.com/octocat/Spoon-Knife
+  > From https://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
 2. 将 `Spon-Knife` 项目合并到当地 Git 项目。 这不会在本地更改任何文件，但会为下一步准备 Git。
diff --git a/translations/zh-CN/content/get-started/using-github/github-command-palette.md b/translations/zh-CN/content/get-started/using-github/github-command-palette.md
index 112ea50bf5..6c6a2c5750 100644
--- a/translations/zh-CN/content/get-started/using-github/github-command-palette.md
+++ b/translations/zh-CN/content/get-started/using-github/github-command-palette.md
@@ -26,10 +26,12 @@ The ability to run commands directly from your keyboard, without navigating thro
 
 ## Opening the {% data variables.product.prodname_command_palette %}
 
-Open the command palette using one of the following keyboard shortcuts:
+Open the command palette using one of the following default keyboard shortcuts:
 - Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
 - Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
+You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)."
+
 When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
 ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
@@ -42,6 +44,12 @@ When you open the command palette, it shows your location at the top left and us
 
 {% endnote %}
 
+### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
+
+
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode.
+
+![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
 ## Navigating with the {% data variables.product.prodname_command_palette %}
 
 You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
@@ -96,7 +104,7 @@ You can use the {% data variables.product.prodname_command_palette %} to run com
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. The default keyboard shortcuts to open the command palette in command mode are <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac). If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -106,6 +114,7 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 4. Use the arrow keys to highlight the command you want and use <kbd>Enter</kbd> to run it.
 
+
 ## Closing the command palette
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
@@ -113,6 +122,8 @@ When the command palette is active, you can use one of the following keyboard sh
 - Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
 - Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.
+
 ## {% data variables.product.prodname_command_palette %} reference
 
 ### Keystroke functions
diff --git a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
index 9732ccb0b3..1506792c34 100644
--- a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
@@ -30,48 +30,48 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 
 | 键盘快捷键                       | 描述                                                                                                                                                                                                                                                            |
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>s</kbd> 或 <kbd>/</kbd> | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。                                                                                                     |
-| <kbd>g</kbd> <kbd>n</kbd>   | 转到您的通知。 更多信息请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 |
-| <kbd>esc</kbd>              | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素                                                                                                                                                                                                                        |
+| <kbd>S</kbd> 或 <kbd>/</kbd> | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。                                                                                                     |
+| <kbd>G</kbd> <kbd>N</kbd>   | 转到您的通知。 更多信息请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 |
+| <kbd>Esc</kbd>              | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素                                                                                                                                                                                                                        |
 
 {% if command-palette %}
 
-<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
 ## 仓库
 
 | 键盘快捷键                     | 描述                                                                                                                                                                                                                                          |
 | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>g</kbd> <kbd>c</kbd> | 转到 **Code（代码）**选项卡                                                                                                                                                                                                                          |
-| <kbd>g</kbd> <kbd>i</kbd> | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。                                                                                                                                                                              |
-| <kbd>g</kbd> <kbd>p</kbd> | 转到 **Pull requests（拉取请求）**选项卡。 For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
-| <kbd>g</kbd> <kbd>a</kbd> | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %}
-| <kbd>g</kbd> <kbd>b</kbd> | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。                                                                                                                                                                   |
-| <kbd>g</kbd> <kbd>w</kbd> | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %}
-| <kbd>g</kbd> <kbd>g</kbd> | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %}
+| <kbd>G</kbd> <kbd>C</kbd> | 转到 **Code（代码）**选项卡                                                                                                                                                                                                                          |
+| <kbd>G</kbd> <kbd>I</kbd> | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。                                                                                                                                                                              |
+| <kbd>G</kbd> <kbd>P</kbd> | 转到 **Pull requests（拉取请求）**选项卡。 For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
+| <kbd>G</kbd> <kbd>A</kbd> | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %}
+| <kbd>G</kbd> <kbd>B</kbd> | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。                                                                                                                                                                   |
+| <kbd>G</kbd> <kbd>W</kbd> | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %}
+| <kbd>G</kbd> <kbd>G</kbd> | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %}
 
 ## 源代码编辑
 
-| 键盘快捷键                                                           | 描述                                                                                                                                                                            |
-| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
-| <kbd>.</kbd>                                                    | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
-| <kbd>control b</kbd> 或 <kbd>command b</kbd>                     | 插入 Markdown 格式用于粗体文本                                                                                                                                                          |
-| <kbd>control i</kbd> 或 <kbd>command i</kbd>                     | 插入 Markdown 格式用于斜体文本                                                                                                                                                          |
-| <kbd>control k</kbd> 或 <kbd>command k</kbd>                     | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>        | Inserts Markdown formatting for an ordered list                                                                                                                               |
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>        | Inserts Markdown formatting for an unordered list                                                                                                                             |
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>         | Inserts Markdown formatting for a quote{% endif %}
-| <kbd>e</kbd>                                                    | 在 **Edit file（编辑文件）**选项卡中打开源代码文件                                                                                                                                              |
-| <kbd>control f</kbd> 或 <kbd>command f</kbd>                     | 开始在文件编辑器中搜索                                                                                                                                                                   |
-| <kbd>control g</kbd> 或 <kbd>command g</kbd>                     | 查找下一个                                                                                                                                                                         |
-| <kbd>control shift g</kbd> or <kbd>command shift g</kbd>        | 查找上一个                                                                                                                                                                         |
-| <kbd>control shift f</kbd> or <kbd>command option f</kbd>       | 替换                                                                                                                                                                            |
-| <kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | 全部替换                                                                                                                                                                          |
-| <kbd>alt g</kbd>                                                | 跳至行                                                                                                                                                                           |
-| <kbd>control z</kbd> 或 <kbd>command z</kbd>                     | 撤消                                                                                                                                                                            |
-| <kbd>control y</kbd> 或 <kbd>command y</kbd>                     | 重做                                                                                                                                                                            |
-| <kbd>command shift p</kbd>                                      | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换                                                                                                                      |
-| <kbd>control s</kbd> 或 <kbd>command s</kbd>                     | 填写提交消息                                                                                                                                                                        |
+| 键盘快捷键                                                                                                                                           | 描述                                                                                                                                                                            |
+| ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| <kbd>.</kbd>                                                                                                                                    | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                                     | 插入 Markdown 格式用于粗体文本                                                                                                                                                          |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                                     | 插入 Markdown 格式用于斜体文本                                                                                                                                                          |
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                     | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux)                   | Inserts Markdown formatting for an ordered list                                                                                                                               |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux)                   | Inserts Markdown formatting for an unordered list                                                                                                                             |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux)                   | Inserts Markdown formatting for a quote{% endif %}
+| <kbd>E</kbd>                                                                                                                                    | 在 **Edit file（编辑文件）**选项卡中打开源代码文件                                                                                                                                              |
+| <kbd>Command</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>F</kbd> (Windows/Linux)                                                     | 开始在文件编辑器中搜索                                                                                                                                                                   |
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                                     | 查找下一个                                                                                                                                                                         |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Windows/Linux)                   | 查找上一个                                                                                                                                                                         |
+| <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F</kbd> (Windows/Linux)                  | 替换                                                                                                                                                                            |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>R</kbd> (Windows/Linux) | 全部替换                                                                                                                                                                          |
+| <kbd>Alt</kbd>+<kbd>G</kbd>                                                                                                                     | 跳至行                                                                                                                                                                           |
+| <kbd>Command</kbd>+<kbd>Z</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Z</kbd> (Windows/Linux)                                                     | 撤消                                                                                                                                                                            |
+| <kbd>Command</kbd>+<kbd>Y</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Y</kbd> (Windows/Linux)                                                     | 重做                                                                                                                                                                            |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>                                                                                                | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换                                                                                                                      |
+| <kbd>Command</kbd>+<kbd>S</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>S</kbd> (Windows/Linux)                                                     | 填写提交消息                                                                                                                                                                        |
 
 有关更多键盘快捷键，请参阅 [CodeMirror 文档](https://codemirror.net/doc/manual.html#commands)。
 
@@ -79,149 +79,151 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 
 | 键盘快捷键        | 描述                                                                                      |
 | ------------ | --------------------------------------------------------------------------------------- |
-| <kbd>t</kbd> | 激活文件查找器                                                                                 |
-| <kbd>l</kbd> | 跳至代码中的某一行                                                                               |
-| <kbd>w</kbd> | 切换到新分支或标记                                                                               |
-| <kbd>y</kbd> | 将 URL 展开为其规范形式。 更多信息请参阅“[获取文件的永久链接](/articles/getting-permanent-links-to-files)”。       |
-| <kbd>i</kbd> | 显示或隐藏有关差异的评论。 更多信息请参阅“[评论拉取请求的差异](/articles/commenting-on-the-diff-of-a-pull-request)”。 |
-| <kbd>a</kbd> | 在差异上显示或隐藏注释                                                                             |
-| <kbd>b</kbd> | 打开追溯视图。 更多信息请参阅“[跟踪文件中的更改](/articles/tracing-changes-in-a-file)”。                       |
+| <kbd>T</kbd> | 激活文件查找器                                                                                 |
+| <kbd>L</kbd> | 跳至代码中的某一行                                                                               |
+| <kbd>W</kbd> | 切换到新分支或标记                                                                               |
+| <kbd>Y</kbd> | 将 URL 展开为其规范形式。 更多信息请参阅“[获取文件的永久链接](/articles/getting-permanent-links-to-files)”。       |
+| <kbd>I</kbd> | 显示或隐藏有关差异的评论。 更多信息请参阅“[评论拉取请求的差异](/articles/commenting-on-the-diff-of-a-pull-request)”。 |
+| <kbd>A</kbd> | 在差异上显示或隐藏注释                                                                             |
+| <kbd>B</kbd> | 打开追溯视图。 更多信息请参阅“[跟踪文件中的更改](/articles/tracing-changes-in-a-file)”。                       |
 
 ## 评论
 
-| 键盘快捷键                                                    | 描述                                                                                                                                                                           |
-| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>control b</kbd> 或 <kbd>command b</kbd>              | 插入 Markdown 格式用于粗体文本                                                                                                                                                         |
-| <kbd>control i</kbd> 或 <kbd>command i</kbd>              | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>control e</kbd> 或 <kbd>command e</kbd>              | 在行内插入代码或命令的 Markdown 格式{% endif %}
-| <kbd>control k</kbd> 或 <kbd>command k</kbd>              | 插入 Markdown 格式用于创建链接                                                                                                                                                         |
-| <kbd>control shift p</kbd> 或 <kbd>command shift p</kbd>  | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list                                                                                                                              |
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list{% endif %}
-| <kbd>control enter</kbd> or <kbd>command enter</kbd>     | 提交评论                                                                                                                                                                         |
-| <kbd>control .</kbd>，然后 <kbd>control [已保存回复编号]</kbd>     | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>  | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
-| <kbd>control g</kbd> 或 <kbd>command g</kbd>              | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 
+| 键盘快捷键                                                                                                                         | 描述                                                                                                                                                                           |
+| ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                   | 插入 Markdown 格式用于粗体文本                                                                                                                                                         |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | 在行内插入代码或命令的 Markdown 格式{% endif %}
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | 插入 Markdown 格式用于创建链接                                                                                                                                                         |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list                                                                                                                              |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
+| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | 提交评论                                                                                                                                                                         |
+| <kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd>                                         | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                   | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 
 {% endif %}
-| <kbd>r</kbd>                                             | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。                                                                             |
+| <kbd>R</kbd>                                                                                                                  | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。                                                                             |
+
 
 ## 议题和拉取请求列表
 
-| 键盘快捷键                                       | 描述                                                                                                                                                                                          |
-| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>c</kbd>                                | 创建议题                                                                                                                                                                                        |
-| <kbd>control /</kbd> 或 <kbd>command /</kbd> | 将光标聚焦于议题或拉取请求搜索栏。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
-| <kbd>u</kbd>                                | 按作者过滤                                                                                                                                                                                       |
-| <kbd>l</kbd>                                | 按标签过滤或编辑标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                                |
-| <kbd>alt</kbd> 并单击                          | 按标签过滤时，排除标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                               |
-| <kbd>m</kbd>                                | 按里程碑过滤或编辑里程碑。 更多信息请参阅“[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)”。                                                                                          |
-| <kbd>a</kbd>                                | 按受理人过滤或编辑受理人。 更多信息请参阅“[按受理人过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-assignees)”。                                                                                          |
-| <kbd>o</kbd> 或 <kbd>enter</kbd>             | 打开议题                                                                                                                                                                                        |
+| 键盘快捷键                                                                                       | 描述                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>C</kbd>                                                                                | 创建议题                                                                                                                                                                                        |
+| <kbd>Command</kbd>+<kbd>/</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows/Linux) | 将光标聚焦于议题或拉取请求搜索栏。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
+| <kbd>U</kbd>                                                                                | 按作者过滤                                                                                                                                                                                       |
+| <kbd>L</kbd>                                                                                | 按标签过滤或编辑标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                                |
+| <kbd>Alt</kbd> 并单击                                                                          | 按标签过滤时，排除标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                               |
+| <kbd>M</kbd>                                                                                | 按里程碑过滤或编辑里程碑。 更多信息请参阅“[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)”。                                                                                          |
+| <kbd>A</kbd>                                                                                | 按受理人过滤或编辑受理人。 更多信息请参阅“[按受理人过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-assignees)”。                                                                                          |
+| <kbd>O</kbd> or <kbd>Enter</kbd>                                                            | 打开议题                                                                                                                                                                                        |
 
 ## 议题和拉取请求
-| 键盘快捷键                                                       | 描述                                                                                                                                                                                                                                                            |
-| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>q</kbd>                                                | 请求审查者。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review/)”。                                                                                                                                                                                      |
-| <kbd>m</kbd>                                                | 设置里程碑。 更多信息请参阅“[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests/)”。                                                                                                                                                            |
-| <kbd>l</kbd>                                                | 应用标签。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests/)”。                                                                                                                                                                        |
-| <kbd>a</kbd>                                                | 设置受理人。 更多信息请参阅“[分配议题和拉取请求到其他 {% data variables.product.company_short %} 用户](/articles/assigning-issues-and-pull-requests-to-other-github-users/)”。                                                                                                            |
-| <kbd>cmd + shift + p</kbd> 或 <kbd>control + shift + p</kbd> | 在 **Write（撰写）**和 **Preview（预览）**选项卡之间切换{% ifversion fpt or ghec %}
-| <kbd>alt</kbd> 并单击                                          | 从任务列表创建议题时，按住 <kbd>alt</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在当前选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                           |
-| <kbd>shift</kbd> 并点击                                        | 从任务列表创建议题时，按住 <kbd>shift</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                          |
-| <kbd>command</kbd> 或 <kbd>control + shift</kbd> 并点击         | 从任务列表创建议题时，按住 <kbd>command</kbd> 或 <kbd>control + shift</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新窗口中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。{% endif %}
+| 键盘快捷键                                                                                                                         | 描述                                                                                                                                                                                                                                                                                                                                                                                  |
+| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Q</kbd>                                                                                                                  | 请求审查者。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review/)”。                                                                                                                                                                                                                                                                                                            |
+| <kbd>M</kbd>                                                                                                                  | 设置里程碑。 更多信息请参阅“[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests/)”。                                                                                                                                                                                                                                                                                  |
+| <kbd>L</kbd>                                                                                                                  | 应用标签。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests/)”。                                                                                                                                                                                                                                                                                              |
+| <kbd>A</kbd>                                                                                                                  | 设置受理人。 更多信息请参阅“[分配议题和拉取请求到其他 {% data variables.product.company_short %} 用户](/articles/assigning-issues-and-pull-requests-to-other-github-users/)”。                                                                                                                                                                                                                                  |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | 在 **Write（撰写）**和 **Preview（预览）**选项卡之间切换{% ifversion fpt or ghec %}
+| <kbd>Alt</kbd> 并单击                                                                                                            | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                                   |
+| <kbd>Shift</kbd> 并点击                                                                                                          | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                                       |
+| <kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux)                        | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。{% endif %}
 
 ## 拉取请求中的更改
 
-| 键盘快捷键                           | 描述                                                                                                                                                                                                          |
-| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>c</kbd>                    | 在拉取请求中打开提交列表                                                                                                                                                                                                |
-| <kbd>t</kbd>                    | 在拉取请求中打开已更改文件列表                                                                                                                                                                                             |
-| <kbd>j</kbd>                    | 将所选内容在列表中向下移动                                                                                                                                                                                               |
-| <kbd>k</kbd>                    | 将所选内容在列表中向上移动                                                                                                                                                                                               |
-| <kbd>cmd + shift + enter </kbd> | 添加一条有关拉取请求差异的评论                                                                                                                                                                                             |
-| <kbd>alt</kbd> 并单击              | 通过按下 `alt` 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。{% ifversion fpt or ghes or ghae or ghec %}
-| 单击，然后按住 <kbd>shift</kbd> 并单击    | 单击一个行号，按住 <kbd>shift</kbd>，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”
+| 键盘快捷键                                                | 描述                                                                                                                                                                                                                                                                                          |
+| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>C</kbd>                                         | 在拉取请求中打开提交列表                                                                                                                                                                                                                                                                                |
+| <kbd>T</kbd>                                         | 在拉取请求中打开已更改文件列表                                                                                                                                                                                                                                                                             |
+| <kbd>J</kbd>                                         | 将所选内容在列表中向下移动                                                                                                                                                                                                                                                                               |
+| <kbd>K</kbd>                                         | 将所选内容在列表中向上移动                                                                                                                                                                                                                                                                               |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | 添加一条有关拉取请求差异的评论                                                                                                                                                                                                                                                                             |
+| <kbd>Alt</kbd> 并单击                                   | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %}
+| Click, then <kbd>Shift</kbd> and click               | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”
 {% endif %}
 
 ## 项目板
 
 ### 移动列
 
-| 键盘快捷键                                                                                             | 描述          |
-| ------------------------------------------------------------------------------------------------- | ----------- |
-| <kbd>enter</kbd> 或 <kbd>space</kbd>                                                               | 开始移动聚焦的列    |
-| <kbd>escape</kbd>                                                                                 | 取消正在进行的移动   |
-| <kbd>enter</kbd>                                                                                  | 完成正在进行的移动   |
-| <kbd>←</kbd> 或 <kbd>h</kbd>                                                                       | 向左移动列       |
-| <kbd>command + ←</kbd> 或 <kbd>command + h</kbd> 或 <kbd>control + ←</kbd> 或 <kbd>control + h</kbd> | 将列移动到最左侧的位置 |
-| <kbd>→</kbd> 或 <kbd>l</kbd>                                                                       | 向右移动列       |
-| <kbd>command + →</kbd> 或 <kbd>command + l</kbd> 或 <kbd>control + →</kbd> 或 <kbd>control + l</kbd> | 将列移动到最右侧的位置 |
+| 键盘快捷键                                                                                                                                                          | 描述          |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| <kbd>Enter</kbd> or <kbd>Space</kbd>                                                                                                                           | 开始移动聚焦的列    |
+| <kbd>Esc</kbd>                                                                                                                                                 | 取消正在进行的移动   |
+| <kbd>Enter</kbd>                                                                                                                                               | 完成正在进行的移动   |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                                                                                                   | 向左移动列       |
+| <kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | 将列移动到最左侧的位置 |
+| <kbd>→</kbd> or <kbd>L</kbd>                                                                                                                                   | 向右移动列       |
+| <kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | 将列移动到最右侧的位置 |
 
 ### 移动卡片
 
-| 键盘快捷键                                                                                                                             | 描述            |
-| --------------------------------------------------------------------------------------------------------------------------------- | ------------- |
-| <kbd>enter</kbd> 或 <kbd>space</kbd>                                                                                               | 开始移动聚焦的卡片     |
-| <kbd>escape</kbd>                                                                                                                 | 取消正在进行的移动     |
-| <kbd>enter</kbd>                                                                                                                  | 完成正在进行的移动     |
-| <kbd>↓</kbd> 或 <kbd>j</kbd>                                                                                                       | 向下移动卡片        |
-| <kbd>command + ↓</kbd> 或 <kbd>command + j</kbd> 或 <kbd>control + ↓</kbd> 或 <kbd>control + j</kbd>                                 | 将卡片移动到该列的底部   |
-| <kbd>↑</kbd> 或 <kbd>k</kbd>                                                                                                       | 向上移动卡片        |
-| <kbd>command + ↑</kbd> 或 <kbd>command + k</kbd> 或 <kbd>control + ↑</kbd> 或 <kbd>control + k</kbd>                                 | 将卡片移动到该列的顶部   |
-| <kbd>←</kbd> 或 <kbd>h</kbd>                                                                                                       | 将卡片移动到左侧列的底部  |
-| <kbd>shift + ←</kbd> 或 <kbd>shift + h</kbd>                                                                                       | 将卡片移动到左侧列的顶部  |
-| <kbd>command + ←</kbd> 或 <kbd>command + h</kbd> 或 <kbd>control + ←</kbd> 或 <kbd>control + h</kbd>                                 | 将卡片移动到最左侧列的底部 |
-| <kbd>command + shift + ←</kbd> 或 <kbd>command + shift + h</kbd> 或 <kbd>control + shift + ←</kbd> 或 <kbd>control + shift + h</kbd> | 将卡片移动到最左侧列的顶部 |
-| <kbd>→</kbd>                                                                                                                      | 将卡片移动到右侧列的底部  |
-| <kbd>shift + →</kbd> 或 <kbd>shift + l</kbd>                                                                                       | 将卡片移动到右侧列的顶部  |
-| <kbd>command + →</kbd> 或 <kbd>command + l</kbd> 或 <kbd>control + →</kbd> 或 <kbd>control + l</kbd>                                 | 将卡片移动到最右侧列的底部 |
-| <kbd>command + shift + →</kbd> 或 <kbd>command + shift + l</kbd> 或 <kbd>control + shift + →</kbd> 或 <kbd>control + shift + l</kbd> | 将卡片移动到最右侧列的底部 |
+| 键盘快捷键                                                                                                                                                                                                                              | 描述            |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
+| <kbd>Enter</kbd> or <kbd>Space</kbd>                                                                                                                                                                                               | 开始移动聚焦的卡片     |
+| <kbd>Esc</kbd>                                                                                                                                                                                                                     | 取消正在进行的移动     |
+| <kbd>Enter</kbd>                                                                                                                                                                                                                   | 完成正在进行的移动     |
+| <kbd>↓</kbd> or <kbd>J</kbd>                                                                                                                                                                                                       | 向下移动卡片        |
+| <kbd>Command</kbd>+<kbd>↓</kbd> or <kbd>Command</kbd>+<kbd>J</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↓</kbd> or <kbd>Ctrl</kbd>+<kbd>J</kbd> (Windows/Linux)                                                                     | 将卡片移动到该列的底部   |
+| <kbd>↑</kbd> or <kbd>K</kbd>                                                                                                                                                                                                       | 向上移动卡片        |
+| <kbd>Command</kbd>+<kbd>↑</kbd> or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↑</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                                     | 将卡片移动到该列的顶部   |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                                                                                                                                                                       | 将卡片移动到左侧列的底部  |
+| <kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Shift</kbd>+<kbd>H</kbd>                                                                                                                                                                     | 将卡片移动到左侧列的顶部  |
+| <kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux)                                                                     | 将卡片移动到最左侧列的底部 |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | 将卡片移动到最左侧列的顶部 |
+| <kbd>→</kbd>                                                                                                                                                                                                                       | 将卡片移动到右侧列的底部  |
+| <kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Shift</kbd>+<kbd>L</kbd>                                                                                                                                                                     | 将卡片移动到右侧列的顶部  |
+| <kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux)                                                                     | 将卡片移动到最右侧列的底部 |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | 将卡片移动到最右侧列的底部 |
 
 ### 预览卡片
 
 | 键盘快捷键          | 描述       |
 | -------------- | -------- |
-| <kbd>esc</kbd> | 关闭卡片预览窗格 |
+| <kbd>Esc</kbd> | 关闭卡片预览窗格 |
 
 {% ifversion fpt or ghec %}
 ## {% data variables.product.prodname_actions %}
 
-| 键盘快捷键                                                    | 描述                      |
-| -------------------------------------------------------- | ----------------------- |
-| <kbd>command + space </kbd> 或 <kbd>control + space</kbd> | 在工作流程编辑器中，获取对工作流程文件的建议。 |
-| <kbd>g</kbd> <kbd>f</kbd>                                | 转到工作流程文件                |
-| <kbd>shift + t</kbd> 或 <kbd>T</kbd>                      | 切换日志中的时间戳               |
-| <kbd>shift + f</kbd> 或 <kbd>F</kbd>                      | 切换全屏日志                  |
-| <kbd>esc</kbd>                                           | 退出全屏日志                  |
+| 键盘快捷键                                                                                                | 描述                      |
+| ---------------------------------------------------------------------------------------------------- | ----------------------- |
+| <kbd>Command</kbd>+<kbd>Space </kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Space</kbd> (Windows/Linux) | 在工作流程编辑器中，获取对工作流程文件的建议。 |
+| <kbd>G</kbd> <kbd>F</kbd>                                                                            | 转到工作流程文件                |
+| <kbd>Shift</kbd>+<kbd>T</kbd> or <kbd>T</kbd>                                                        | 切换日志中的时间戳               |
+| <kbd>Shift</kbd>+<kbd>F</kbd> or <kbd>F</kbd>                                                        | 切换全屏日志                  |
+| <kbd>Esc</kbd>                                                                                       | 退出全屏日志                  |
 
 {% endif %}
 
 ## 通知
 {% ifversion fpt or ghes or ghae or ghec %}
-| 键盘快捷键                | 描述    |
-| -------------------- | ----- |
-| <kbd>e</kbd>         | 标记为完成 |
-| <kbd>shift + u</kbd> | 标记为未读 |
-| <kbd>shift + i</kbd> | 标记为已读 |
-| <kbd>shift + m</kbd> | 取消订阅  |
+| 键盘快捷键                         | 描述    |
+| ----------------------------- | ----- |
+| <kbd>E</kbd>                  | 标记为完成 |
+| <kbd>Shift</kbd>+<kbd>U</kbd> | 标记为未读 |
+| <kbd>Shift</kbd>+<kbd>I</kbd> | 标记为已读 |
+| <kbd>Shift</kbd>+<kbd>M</kbd> | 取消订阅  |
 
 {% else %}
 
-| 键盘快捷键                                    | 描述    |
-| ---------------------------------------- | ----- |
-| <kbd>e</kbd>、<kbd>I</kbd> 或 <kbd>y</kbd> | 标记为已读 |
-| <kbd>shift + m</kbd>                     | 静音线程  |
+| 键盘快捷键                                        | 描述    |
+| -------------------------------------------- | ----- |
+| <kbd>E</kbd> or <kbd>I</kbd> or <kbd>Y</kbd> | 标记为已读 |
+| <kbd>Shift</kbd>+<kbd>M</kbd>                | 静音线程  |
 {% endif %}
 
 ## 网络图
 
-| 键盘快捷键                                       | 描述     |
-| ------------------------------------------- | ------ |
-| <kbd>←</kbd> 或 <kbd>h</kbd>                 | 向左滚动   |
-| <kbd>→</kbd> 或 <kbd>l</kbd>                 | 向右滚动   |
-| <kbd>↑</kbd> 或 <kbd>k</kbd>                 | 向上滚动   |
-| <kbd>↓</kbd> 或 <kbd>j</kbd>                 | 向下滚动   |
-| <kbd>shift + ←</kbd> 或 <kbd>shift + h</kbd> | 一直向左滚动 |
-| <kbd>shift + →</kbd> 或 <kbd>shift + l</kbd> | 一直向右滚动 |
-| <kbd>shift + ↑</kbd> 或 <kbd>shift + k</kbd> | 一直向上滚动 |
-| <kbd>shift + ↓</kbd> 或 <kbd>shift + j</kbd> | 一直向下滚动 |
+| 键盘快捷键                                                                                      | 描述     |
+| ------------------------------------------------------------------------------------------ | ------ |
+| <kbd>←</kbd> or <kbd>H</kbd>                                                               | 向左滚动   |
+| <kbd>→</kbd> or <kbd>L</kbd>                                                               | 向右滚动   |
+| <kbd>↑</kbd> or <kbd>K</kbd>                                                               | 向上滚动   |
+| <kbd>↓</kbd> or <kbd>J</kbd>                                                               | 向下滚动   |
+| <kbd>Shift</kbd>+<kbd>←</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | 一直向左滚动 |
+| <kbd>Shift</kbd>+<kbd>→</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | 一直向右滚动 |
+| <kbd>Shift</kbd>+<kbd>↑</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>K</kbd> (Windows/Linux) | 一直向上滚动 |
+| <kbd>Shift</kbd>+<kbd>↓</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>J</kbd> (Windows/Linux) | 一直向下滚动 |
diff --git a/translations/zh-CN/content/github/copilot/research-recitation.md b/translations/zh-CN/content/github/copilot/research-recitation.md
index ced0724918..cf4188c1f8 100644
--- a/translations/zh-CN/content/github/copilot/research-recitation.md
+++ b/translations/zh-CN/content/github/copilot/research-recitation.md
@@ -57,9 +57,9 @@ r'^\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d
 过滤后还剩下 473 条建议。 但它们的表现形式非常不同：
 
 1. 有些基本上只是重复另一个通过了过滤的案例。 例如，有时 {% data variables.product.prodname_dotcom %} Copilot 提出建议，开发人员键入一个评论行，然后 {% data variables.product.prodname_dotcom %} Copilot 再次提供一个非常相似的建议。 我从分析中删除了这些作为重复项的案例。
-2. 有些是长而重复的序列。 像下面的示例一样，在培训集的某个地方当然可以找到重复的 `‘<p>’` 块 ：<br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> 这样的建议可能会有所帮助（测试案例、正则表达式）或没有帮助（像本案例，我怀疑）。 但无论如何，它们并不符合我开始调查时所想到的死记硬背学习的想法。
+2. 有些是长而重复的序列。 Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br>![Example repetitions](/assets/images/help/copilot/example_repetitions.png)<br> Such suggestions can be helpful (test cases, regular expressions) or not helpful (like this case, I suspect). 但无论如何，它们并不符合我开始调查时所想到的死记硬背学习的想法。
 3. 有些是标准库存，如自然数字、质数、股市股票代码或希腊字母： <br>![希腊字母示例](/assets/images/help/copilot/example_greek.png)
-4. 有些是常见的、直接的方式，甚至是普遍的方式，以很少的自然自由度做事。 例如， 下面的中间部分触发了我使用 BeautifulSoup 包解析维基百科列表的标准方法。 事实上， 在 {% data variables.product.prodname_dotcom %} Copilot 的培训数据<sup id="anchor5">[5](#footnote5)</sup> 中找到的最佳匹配片段使用这种代码解析不同的文章，并继续根据结果做不同的事情。 <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>这也不符合我对引文的想法。 这有点像有人说“我要把垃圾拿出来；我很快就会回来的”— 这是事实陈述，不是引文，尽管这句话以前已经说过很多次了。
+4. 有些是常见的、直接的方式，甚至是普遍的方式，以很少的自然自由度做事。 For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a Wikipedia list. 事实上， 在 {% data variables.product.prodname_dotcom %} Copilot 的培训数据<sup id="anchor5">[5](#footnote5)</sup> 中找到的最佳匹配片段使用这种代码解析不同的文章，并继续根据结果做不同的事情。 <br>![Example of Beautiful Soup](/assets/images/help/copilot/example_beautiful_soup.png) <br>这也不符合我对引文的想法。 这有点像有人说“我要把垃圾拿出来；我很快就会回来的”— 这是事实陈述，不是引文，尽管这句话以前已经说过很多次了。
 5. 然后还有所有其他情况。 代码或评论中至少有一些特定重叠。 这些是我最感兴趣的，也是我从现在开始要集中精力的。
 
 此存储桶必须有一些边缘案例<sup id="anchor6">[6](#footnote6)</sup>，并且您的里程可能因您认为应分类的方式而有所不同。 也许你甚至一开始就不同意整套存储桶。
diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md
index 3d51889658..c6652f4958 100644
--- a/translations/zh-CN/content/github/index.md
+++ b/translations/zh-CN/content/github/index.md
@@ -12,8 +12,6 @@ versions:
   ghae: '*'
 children:
   - /copilot
-  - /customizing-your-github-workflow
-  - /extending-github
   - /site-policy
   - /site-policy-deprecated
 ---
diff --git a/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md b/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md
index 8f72fcd4e0..217c3a1869 100644
--- a/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md
+++ b/translations/zh-CN/content/github/site-policy/github-government-takedown-policy.md
@@ -30,5 +30,8 @@ GitHub 有时会收到政府要求，要求我们删除在其地方管辖区被
 ## 如果我们在 gov-takedown 仓库中发布通知，它意味着什么？
 这意味着我们在指定日期收到了通知， 但*不*意味着内容是非法或错误的， 也*不*意味着通知中所指的用户犯了任何错误。 我们并不对政府请求的正误做出或暗示任何判断。 我们发布这些通知和请求只是提供信息。
 
+## Government takedowns based on violations of GitHub's Terms of Service
+In some cases, GitHub receives reports from government officials of violations of GitHub's Terms of Service. We process those violations as we would process a Terms-of-Service violation reported by anyone else. However, we notify the affected users that the report came from a government and, as with any other case, allow them the opportunity to appeal.
+
 ## 透明度报告
-除了在我们的 gov-takedowns 仓库中发布政府删除通知外，我们的透明度报告中也会报告这些通知。 我们还会在透明度报告中跟踪并报告基于违反 GitHub 服务条款的政府删除。 我们处理这些违规就像处理任何其他人报告的服务条款违规一样。
+In addition to posting government takedown notices in our `github/gov-takedowns` repository, we report on them in our transparency report. 我们还会在透明度报告中跟踪并报告基于违反 GitHub 服务条款的政府删除。
diff --git a/translations/zh-CN/content/issues/index.md b/translations/zh-CN/content/issues/index.md
index deeac26321..2164c69112 100644
--- a/translations/zh-CN/content/issues/index.md
+++ b/translations/zh-CN/content/issues/index.md
@@ -33,6 +33,7 @@ featuredLinks:
     - title: Issue Forms for open source – Luke Hefson
       href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
   videosHeading: GitHub Universe 2021 videos
+product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
 layout: product-landing
 beta_product: false
 versions:
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-task-lists.md
index af1f4b3f9f..08d8c0dc90 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -76,5 +76,5 @@ topics:
 
 ## 延伸阅读
 
-* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% if code-scanning-task-lists %}
 * "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 180dfe1183..c356a9cc34 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -143,7 +143,7 @@ When you create an issue from a discussion, the contents of the discussion post
 | `projects`  | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` 创建标题为 "Bug fix" 的议题并将其添加到组织的项目板 1。                                                                                                                                                     |
 | `模板`        | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` 使用模板在议题正文中创建议题。 `template` 查询参数支持仓库根目录 `docs/` 或 `.github/` 的 `ISSUE_TEMPLATE` 子目录中存储的模板。 更多信息请参阅“[使用模板鼓励有用的议题和拉取请求](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)”。 |
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
index b45d3acee1..8efda0479f 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
@@ -1,6 +1,6 @@
 ---
 title: 保护组织安全
-intro: '组织所有者有多项功能来帮助保护其项目和数据的安全。 如果您是组织的所有者，应定期检查组织的审核日志{% ifversion not ghae %}、成员 2FA 状态{% endif %} 和应用程序设置，以确保没有未授权或恶意的活动。'
+intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -14,14 +14,8 @@ topics:
   - Organizations
   - Teams
 children:
-  - /viewing-whether-users-in-your-organization-have-2fa-enabled
-  - /preparing-to-require-two-factor-authentication-in-your-organization
-  - /requiring-two-factor-authentication-in-your-organization
-  - /managing-security-and-analysis-settings-for-your-organization
-  - /managing-allowed-ip-addresses-for-your-organization
-  - /restricting-email-notifications-for-your-organization
-  - /reviewing-the-audit-log-for-your-organization
-  - /reviewing-your-organizations-installed-integrations
+  - /managing-two-factor-authentication-for-your-organization
+  - /managing-security-settings-for-your-organization
 shortTitle: 组织安全
 ---
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
new file mode 100644
index 0000000000..513d2880c2
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Accessing compliance reports for your organization
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Teams
+permissions: Organization owners can access compliance reports for the organization.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+
+{% data reusables.security.compliance-report-list %}
+
+## Accessing compliance reports for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "Compliance reports", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## 延伸阅读
+
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
new file mode 100644
index 0000000000..6c813260f9
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing security settings for your organization
+shortTitle: Manage security settings
+intro: 'You can manage security settings and review the audit log{% ifversion ghec %}, compliance reports,{% endif %} and integrations for your organization.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-security-and-analysis-settings-for-your-organization
+  - /managing-allowed-ip-addresses-for-your-organization
+  - /restricting-email-notifications-for-your-organization
+  - /reviewing-the-audit-log-for-your-organization
+  - /accessing-compliance-reports-for-your-organization
+  - /reviewing-your-organizations-installed-integrations
+---
+
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
new file mode 100644
index 0000000000..365e0a9e9d
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -0,0 +1,85 @@
+---
+title: 管理组织允许的 IP 地址
+intro: 您可以通过配置允许连接的 IP 地址列表来限制对组织资产的访问。
+product: '{% data reusables.gated-features.allowed-ip-addresses %}'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 管理允许的 IP 地址
+---
+
+组织所有者可以管理组织允许的 IP 地址。
+
+## 关于允许的 IP 地址
+
+您可以通过为特定 IP 地址配置允许列表来限制对组织资产的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
+
+如果您设置了允许列表，您还可以选择将为组织中安装的 {% data variables.product.prodname_github_apps %} 配置的任何 IP 地址自动添加到允许列表中。 {% data variables.product.prodname_github_app %} 的创建者可以为其应用程序配置允许列表，指定应用程序运行的 IP 地址。 通过将允许列表继承到您的列表中，您可以避免申请中的连接请求被拒绝。 更多信息请参阅“[允许 {% data variables.product.prodname_github_apps %} 访问](#allowing-access-by-github-apps)”。
+
+您还可以为企业帐户中的组织配置允许的 IP 地址。 更多信息请参阅“[在企业中实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)”。
+
+## 添加允许的 IP 地址
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+
+## 启用允许的 IP 地址
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. 单击 **Save（保存）**。
+
+## 允许 {% data variables.product.prodname_github_apps %} 访问
+
+如果您设置允许列表，您还可以选择将为组织中安装的 {% data variables.product.prodname_github_apps %} 配置的任何 IP 地址自动添加到允许列表中。
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+有关如何为您创建的 {% data variables.product.prodname_github_app %} 创建允许列表的更多信息，请参阅“[管理 GitHub 应用程序允许的 IP 地址](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)”。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. 在“IP allow list（IP允许列表）”下，选择 **Enable IP allow list configuration for installed GitHub Apps（启用已安装 GitHub 应用程序的 IP 允许列表配置）**。 ![允许 GitHub 应用程序 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. 单击 **Save（保存）**。
+
+## 编辑允许的 IP 地址
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+1. 单击 **Update（更新）**。
+
+## 删除允许的 IP 地址
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
+
+{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
new file mode 100644
index 0000000000..f3d678c3aa
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -0,0 +1,171 @@
+---
+title: 管理组织的安全性和分析设置
+intro: '您可以控制功能以保护组织在 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。'
+permissions: Organization owners can manage security and analysis settings for repositories in the organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 管理安全和分析
+---
+
+## 关于安全性和分析设置的管理
+
+{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 {% ifversion ghec %}如果您拥有 {% data variables.product.prodname_GH_advanced_security %} 许可，则您还可以管理对这些功能的访问。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## 显示安全和分析设置
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+
+显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。
+
+{% ifversion ghec %}如果您的组织属于具有 {% data variables.product.prodname_GH_advanced_security %} 许可的企业，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
+
+{% ifversion ghes > 3.0 %}如果您具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
+
+{% ifversion ghae %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
+
+## 为所有现有仓库启用或禁用功能
+
+您可以启用或禁用所有仓库的功能。
+{% ifversion fpt or ghec %}您的更改对组织中仓库的影响取决于其可见性：
+
+- **依赖项图** - 您的更改仅影响私有仓库，因为该功能对公共仓库始终启用。
+- **{% data variables.product.prodname_dependabot_alerts %}** - 您的更改影响所有仓库。
+- **{% data variables.product.prodname_dependabot_security_updates %}** - 您的更改影响所有仓库。
+{%- ifversion ghec %}
+- **{% data variables.product.prodname_GH_advanced_security %}** - 您的更改仅影响私有仓库，因为 {% data variables.product.prodname_GH_advanced_security %} 和相关功能对公共仓库始终启用。
+- **{% data variables.product.prodname_secret_scanning_caps %}** - 您的更改仅影响还启用了 {% data variables.product.prodname_GH_advanced_security %} 的私有仓库。 {% data variables.product.prodname_secret_scanning_caps %} 对公共仓库始终启用。
+{% endif %}
+
+{% endif %}
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
+2. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 {% ifversion ghes > 3.0 or ghec %}如果您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，对“{% data variables.product.prodname_GH_advanced_security %}”的控制将会禁用。{% endif %}
+   {% ifversion fpt %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   {% endif %}
+   {% ifversion ghes > 3.2 %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% ifversion ghae %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+3. （可选）为组织中的新仓库默认启用该功能。
+   {% ifversion fpt or ghec %}
+   ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![新仓库的"Enable by default（默认启用）"选项](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion fpt or ghes = 3.0 or ghec %}
+4. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。
+   {% ifversion fpt or ghec %}
+   ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![用于禁用或启用功能的按钮](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   {% endif %}
+   {% endif %}
+   {% ifversion ghae or ghes > 3.0 %}
+3. 单击 **Enable/Disable all（全部启用/禁用）**或 **Enable/Disable for eligible repositories（对合格的仓库启用/禁用）**以确认更改。 ![用于为组织中所有符合条件的仓库启用功能的按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% endif %}
+
+   {% data reusables.security.displayed-information %}
+
+## 添加新仓库时自动启用或禁用功能
+
+1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
+2. 在功能右边的“Configure security and analysis features（配置安全性和分析功能）”下，默认为组织中的新仓库{% ifversion fpt or ghec %} 或所有私有仓库{% endif %} 启用或禁用该功能。
+   {% ifversion fpt %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.1 or ghes = 3.2 %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% ifversion ghes = 3.0 %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   {% endif %}
+
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
+
+## 允许 {% data variables.product.prodname_dependabot %} 访问私有依赖项
+
+{% data variables.product.prodname_dependabot %} 可以检查项目中过时的依赖项引用，并自动生成拉取请求来更新它们。 为此，{% data variables.product.prodname_dependabot %} 必须有权访问所有目标依赖项文件。 通常，如果一个或多个依赖项无法访问，版本更新将失败。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot %} 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。
+
+默认情况下，{% data variables.product.prodname_dependabot %} 无法更新位于私有仓库或私有仓库注册表中的依赖项。 但是，如果依赖项位于与使用该依赖项之项目相同的组织内的私有 {% data variables.product.prodname_dotcom %} 仓库中，则可以通过授予对主机仓库的访问权限来允许 {% data variables.product.prodname_dependabot %} 成功更新版本。
+
+如果您的代码依赖于私有注册表中的软件包，您可以在仓库级别进行配置，允许 {% data variables.product.prodname_dependabot %} 更新这些依赖项的版本。 可通过将身份验证详细信息添加到仓库的 _dependabot.yml_ 文件来做到这一点。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)。”
+
+要允许 {% data variables.product.prodname_dependabot %} 访问私有 {% data variables.product.prodname_dotcom %} 仓库：
+
+1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
+1. 在“{% data variables.product.prodname_dependabot %} 私有仓库访问”下，单击 **Add private repositories（添加私有仓库）**或 **Add internal and private repositories（添加内部和私有仓库）**。 ![添加仓库按钮](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. 开始键入要允许的仓库的名称。 ![带有过滤条件下拉列表的仓库搜索字段](/assets/images/help/organizations/dependabot-private-repo-choose.png)
+1. 单击您想要允许的仓库。
+
+1. （可选）要从列表中删除仓库，在仓库右侧单击 {% octicon "x" aria-label="The X icon" %}。 !["X" 按钮来删除仓库。](/assets/images/help/organizations/dependabot-private-repository-list.png)
+{% endif %}
+
+{% ifversion ghes > 3.0 or ghec %}
+
+## 从组织中的个别仓库中移除对 {% data variables.product.prodname_GH_advanced_security %} 的访问权限
+
+您可以从仓库的“Settings（设置）”选项卡管理对仓库 {% data variables.product.prodname_GH_advanced_security %} 功能的访问。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 但您也可以从“Settings（设置）”选项卡对仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能。
+
+1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
+1. 要查看您组织中启用 {% data variables.product.prodname_GH_advanced_security %} 的所有仓库的列表，请滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) 表格列出了每个仓库的唯一提交者数量。 这是您可以通过移除 {% data variables.product.prodname_GH_advanced_security %} 访问权限释放的席位数。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)”。
+1. 要从仓库删除对 {% data variables.product.prodname_GH_advanced_security %} 的访问，并释放任何提交者使用的对仓库唯一的席位，请单击相邻的 {% octicon "x" aria-label="X symbol" %}。
+1. 在确认对话框中，单击击 **Remove repository（移除仓库）** 以移除对 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限。
+
+{% note %}
+
+**注意：**如果移除对仓库 {% data variables.product.prodname_GH_advanced_security %} 的访问权限， 您应该与受影响的开发团队进行沟通，以便他们知道改变的意图。 这确保他们不会浪费时间调试运行失败的代码扫描。
+
+{% endnote %}
+
+{% endif %}
+
+## 延伸阅读
+
+- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”
+- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..d70ff69e32
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,47 @@
+---
+title: 限制组织的电子邮件通知
+intro: 为防止组织信息泄露到个人电子邮件帐户，您可以限制成员可以接收有关组织活动的电子邮件通知的域。
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '>=3.2'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: 限制电子邮件通知
+---
+
+## 关于电子邮件限制
+
+当在组织中启用受限制的电子邮件通知时，成员只能使用与已验证或批准的域关联的电子邮件地址接收有关组织活动的电子邮件通知。 更多信息请参阅“[验证或批准组织的域](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”。
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+外部协作者不受限于已验证或批准域的电子邮件通知。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+
+如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证或批准域的通知之外，还能够接收来自企业帐户的任何已验证或批准域的通知。 更多信息请参阅“[验证或批准企业的域](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)”。
+
+## 限制电子邮件通知
+
+在限制组织的电子邮件通知之前，您必须至少验证或批准组织的一个域名，或者企业所有者必须已验证或批准至少一个企业帐户域。
+
+有关验证和批准组织域名的更多信息，请参阅“[验证或批准组织域名](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
new file mode 100644
index 0000000000..562df5e1c8
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -0,0 +1,772 @@
+---
+title: 审查组织的审核日志
+intro: 审核日志允许组织管理员快速审查组织成员执行的操作。 其中包含操作执行人、操作内容和执行时间等详细信息。
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-the-audit-log-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization
+  - /organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 审核审计日志
+---
+
+## 访问审核日志
+
+The audit log lists events triggered by activities that affect your organization within the current month and previous six months. 只有所有者才能访问组织的审核日志。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+
+## 搜索审核日志
+
+{% data reusables.audit_log.audit-log-search %}
+
+### 基于执行的操作搜索
+
+要搜索特定事件，请在查询中使用 `action` 限定符。 审核日志中列出的操作分为以下类别：
+
+| 类别名称                                                                                                                                                                                      | 描述                                                                                                                                                                                                                                                          |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`帐户`](#account-category-actions)                                                                                                                                                         | 包含与组织帐户相关的所有活动。                                                                                                                                                                                                                                             |
+| [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                    | 包含与 {% data variables.product.prodname_advisory_database %} 中安全通告的贡献者积分相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。                              |
+| [`计费，帐单`](#billing-category-actions)                                                                                                                                                      | 包含与组织帐单相关的所有活动。                                                                                                                                                                                                                                             |
+| [`business`](#business-category-actions)                                                                                                                                                  | 包含与企业业务设置相关的活动。                                                                                                                                                                                                                                             |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                              | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in existing repositories. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                            | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.                                                                                        |
+| [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                            | 包含现有仓库中 {% data variables.product.prodname_dependabot_security_updates %} 的组织级配置活动。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)。” |
+| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions)                                                                                        | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
+| [`dependency_graph`](#dependency_graph-category-actions)                                                                                                                                  | 包含仓库依赖项图的组织级配置活动。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。                                                                                                                                           |
+| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions)                                                                                                              | 包含组织新建仓库的组织级配置活动。{% endif %}
+| [`discussion_post`](#discussion_post-category-actions)                                                                                                                                    | 包含与发布到团队页面的讨论相关的所有活动。                                                                                                                                                                                                                                       |
+| [`discussion_post_reply`](#discussion_post_reply-category-actions)                                                                                                                        | 包含与发布到团队页面的讨论回复相关的所有活动。{% ifversion fpt or ghes or ghec %}
+| [`企业`](#enterprise-category-actions)                                                                                                                                                      | 包含与企业设置相关的活动。                                                                                                                                                                                                                                               |{% endif %}
+| [`挂钩`](#hook-category-actions)                                                                                                                                                            | 包含与 web 挂钩相关的所有活动。                                                                                                                                                                                                                                          |
+| [`integration_installation_request`](#integration_installation_request-category-actions)                                                                                                  | 包含与组织成员请求所有者批准用于组织的集成相关的所有活动。                                                                                                                                                                                                                               |
+| [`ip_allow_list`](#ip_allow_list)                                                                                                                                                         | Contains activities related to enabling or disabling the IP allow list for an organization.                                                                                                                                                                 |
+| [`ip_allow_list_entry`](#ip_allow_list_entry)                                                                                                                                             | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.                                                                                                                                           |
+| [`议题`](#issue-category-actions)                                                                                                                                                           | 包含与删除议题相关的活动。                                                                                                                                                                                                                                               |{% ifversion fpt or ghec %}
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions)                                                                                                    | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。                                                                                                                                                                                       |
+| [`marketplace_listing`](#marketplace_listing-category-actions)                                                                                                                            | 包含与在 {% data variables.product.prodname_marketplace %} 中上架应用程序相关的所有活动。{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`members_can_create_pages`](#members_can_create_pages-category-actions)                                                                                                                  | 包含与管理组织仓库的 {% data variables.product.prodname_pages %} 站点发布相关的所有活动。 更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。  |{% endif %}
+| [`org`](#org-category-actions)                                                                                                                                                            | 包含与组织成员身份相关的活动。{% ifversion ghec %}
+| [`org_credential_authorization`](#org_credential_authorization-category-actions)                                                                                                          | 包含与授权凭据以用于 SAML 单点登录相关的所有活动。{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
+| [`organization_label`](#organization_label-category-actions)                                                                                                                              | 包含与组织中仓库的默认标签相关的所有活动。{% endif %}
+| [`oauth_application`](#oauth_application-category-actions)                                                                                                                                | 包含与 OAuth 应用程序相关的所有活动。{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`包`](#packages-category-actions)                                                                                                                                                         | 包含与 {% data variables.product.prodname_registry %} 相关的所有活动。{% endif %}{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions)                                                                                                                                      | 包含与组织如何支付 GitHub 相关的所有活动。{% endif %}
+| [`profile_picture`](#profile_picture-category-actions)                                                                                                                                    | 包含与组织的头像相关的所有活动。                                                                                                                                                                                                                                            |
+| [`project`](#project-category-actions)                                                                                                                                                    | 包含与项目板相关的所有活动。                                                                                                                                                                                                                                              |
+| [`protected_branch`](#protected_branch-category-actions)                                                                                                                                  | 包含与受保护分支相关的所有活动。                                                                                                                                                                                                                                            |
+| [`repo`](#repo-category-actions)                                                                                                                                                          | 包含与组织拥有的仓库相关的所有活动。{% ifversion fpt or ghec %}
+| [`repository_advisory`](#repository_advisory-category-actions)                                                                                                                            | 包含与 {% data variables.product.prodname_advisory_database %} 中的安全通告相关的仓库级活动。  更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。                                 |
+| [`repository_content_analysis`](#repository_content_analysis-category-actions)                                                                                                            | 包含与[启用或禁用私有仓库的数据使用](/articles/about-github-s-use-of-your-data)相关的所有活动。{% endif %}{% ifversion fpt or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions)                                                                                                            | 包含与启用或禁用依赖项图相关的仓库级活动                                                                                                                                                                                                                                        |
+| {% ifversion fpt or ghec %}私有{% endif %}仓库。 更多信息请参阅“[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。{% endif %}{% ifversion ghes or ghae or ghec %} |                                                                                                                                                                                                                                                             |
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions)                                                                                                              | 包含与密码扫描相关的仓库级活动。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。                                                                                                                                                               |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions)                                                                                                      | 包含与[有漏洞依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)相关的所有活动。{% endif %}{% ifversion fpt or ghec %}
+| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions)                                                                                                    | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
+| [`角色`](#role-category-actions)                                                                                                                                                            | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`secret_scanning`](#secret_scanning-category-actions)                                                                                                                                    | 包含现有仓库中密码扫描的组织级配置活动。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。                                                                                                                                                           |
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions)                                                                                                                | 包含组织新建仓库中密码扫描的组织级配置活动。                                                                                                                                                                                                                                      |{% endif %}{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions)                                                                                                                                                  | 包含与与赞助者按钮相关的所有事件（请参阅“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %}
+| [`团队`](#team-category-actions)                                                                                                                                                            | 包含与您的组织中的团队相关的所有活动。                                                                                                                                                                                                                                         |
+| [`team_discussions`](#team_discussions-category-actions)                                                                                                                                  | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| [`工作流程`](#workflows-category-actions)                                                                                                                                                     | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %}
+
+您可以使用这些词搜索特定的操作集。 例如：
+
+  * `action:team` 会找到团队类别中的所有事件。
+  * `-action:hook` 会排除 web 挂钩类别中的所有事件。
+
+每个类别都有一组可进行过滤的关联操作。 例如：
+
+  * `action:team.create` 会找到团队创建处的所有事件。
+  * `-action:hook.events_changed` 会排除 web 挂钩上事件已经改动的所有事件。
+
+### 基于操作时间搜索
+
+使用 `created` 限定符在审核日志中根据事件发生的时间过滤事件。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+例如：
+
+  * `created:2014-07-08` 会找到在 2014 年 7 月 8 日发生的所有事件。
+  * `created:>=2014-07-08` 查找在 2014 年 7 月 8 日或之后发生的所有事件。
+  * `created:<=2014-07-08` 查找在 2014 年 7 月 8 日或之前发生的所有事件。
+  * `created:2014-07-01..2014-07-31` 会找到在 2014 年 7 月发生的所有事件。
+
+
+{% note %}
+
+**Note**: The audit log contains data for the current month and every day of the previous six months.
+
+{% endnote %}
+
+### 基于位置搜索
+
+使用限定符 `country`，您可以在审核日志中根据发生事件的国家/地区过滤事件。 您可以使用国家/地区的两字母短代码或完整名称。 请注意，名称中包含空格的国家/地区需要加引号。 例如：
+
+  * `country:de` 会找到在德国发生的所有事件。
+  * `country:Mexico` 会找到在墨西哥发生的所有事件。
+  * `country:"United States"` 会找到在美国发生的所有事件。
+
+{% ifversion fpt or ghec %}
+## 导出审核日志
+
+{% data reusables.audit_log.export-log %}
+{% data reusables.audit_log.exported-log-keys-and-values %}
+{% endif %}
+
+## 使用审核日志 API
+
+您可以使用 GraphQL API{% ifversion fpt or ghec %} 或 REST API{% endif %} 与审核日志交互。
+
+{% ifversion fpt or ghec %}
+The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+
+### 使用 GraphQL API
+
+{% endif %}
+
+{% note %}
+
+**注**：审核日志 GraphQL API 可用于使用 {% data variables.product.prodname_enterprise %} 的组织。 {% data reusables.gated-features.more-info-org-products %}
+
+{% endnote %}
+
+为确保知识产权得到保护并保持组织的合规，您可以使用审核日志 GraphQL API 保留审核日志数据的副本并监控：
+{% data reusables.audit_log.audit-log-api-info %}
+
+{% ifversion fpt or ghec %}
+请注意，您不能使用 GraphQL API 检索 Git 事件。 要检索 Git 事件，请改为使用 REST API。 更多信息请参阅“[`git` 类操作](#git-category-actions)”。
+{% endif %}
+
+GraphQL 响应可包含长达 90 至 120 天的数据。
+
+例如，您可以创建 GraphQL 请求以查看添加到组织的所有新组织成员。 更多信息请参阅“[GraphQL API 审核日志]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)”。
+
+{% ifversion fpt or ghec %}
+
+### 使用 REST API
+
+{% note %}
+
+**注**：审核日志 REST API 可供 {% data variables.product.prodname_ghe_cloud %} 用户使用。
+
+{% endnote %}
+
+为确保知识产权得到保护并保持组织的合规，您可以使用审核日志 REST API 保留审核日志数据的副本并监控：
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+有关审核日志 REST API 的更多信息，请参阅“[组织](/rest/reference/orgs#get-the-audit-log-for-an-organization)”。
+
+{% endif %}
+
+## 审核日志操作
+
+审核日志中记录为事件的一些最常见操作的概述。
+
+{% ifversion fpt or ghec %}
+### `account` 类操作
+
+| 操作                            | 描述                                                                                                                   |
+| ----------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `billing_plan_change`         | 当组织的[结算周期](/articles/changing-the-duration-of-your-billing-cycle)发生更改时触发。                                            |
+| `plan_change`                 | 当组织的[订阅](/articles/about-billing-for-github-accounts)发生更改时触发。                                                        |
+| `pending_plan_change`         | 当组织所有者或帐单管理员[取消或降级付费订阅](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/)时触发。                 |
+| `pending_subscription_change` | 当 [{% data variables.product.prodname_marketplace %} 免费试用开始或到期](/articles/about-billing-for-github-marketplace/)时触发。 |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `advisory_credit` 类操作
+
+| 操作        | 描述                                                                                                         |
+| --------- | ---------------------------------------------------------------------------------------------------------- |
+| `accept`  | 当有人接受安全通告的积分时触发。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 |
+| `create`  | 当安全通告的管理员将某人添加到积分部分时触发。                                                                                    |
+| `decline` | 当有人拒绝安全通告的积分时触发。                                                                                           |
+| `destroy` | 当安全通告的管理员将某人从积分部分删除时触发。                                                                                    |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `billing` 类操作
+
+| 操作                    | 描述                                                                                                           |
+| --------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `change_billing_type` | 当组织[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 |
+| `change_email`        | 当组织的[帐单电子邮件地址](/articles/setting-your-billing-email)发生更改时触发。                                                 |
+{% endif %}
+
+### `business` 类操作
+
+| 操作                                     | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | 为企业改变需要批准来自公共复刻的工作流程的设置时触发。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)”。{% endif %}
+| `set_actions_retention_limit`          | 为企业改变 {% data variables.product.prodname_actions %} 构件和日志的保留期时触发。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)”。{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`         | 更改私有仓库复刻上的工作流程策略时触发。 For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %}
+
+{% ifversion fpt or ghec %}
+### `codespaces` 类操作
+
+| 操作                           | 描述                                                                                                                                                                                              |
+| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                     | 当用户[创建代码空间](/github/developing-online-with-codespaces/creating-a-codespace)时触发。                                                                                                                 |
+| `resume`                     | 当用户恢复暂停的代码空间时触发。                                                                                                                                                                                |
+| `delete`                     | 当用户[删除代码空间](/github/developing-online-with-codespaces/deleting-a-codespace)时触发。                                                                                                                 |
+| `create_an_org_secret`       | 当用户为 [{% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) 创建组织级密钥时触发  |
+| `update_an_org_secret`       | 当用户为 [{% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) 更新组织级密钥时触发。 |
+| `remove_an_org_secret`       | 当用户为 [{% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) 删除组织级密钥时触发。 |
+| `manage_access_and_security` | 当用户更新[代码空间可以访问的仓库](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)时触发。                                                                                   |
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.2 %}
+### `dependabot_alerts` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                                                                                                                           |
+| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                          |
+
+### `dependabot_alerts_new_repos` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                                                                                                                      |
+| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                          |
+
+### `dependabot_security_updates` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                               |
+| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | 当组织所有者对所有现有仓库禁用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | 当组织所有者对所有现有仓库启用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。                                                                                                                                         |
+
+### `dependabot_security_updates_new_repos` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                              |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | 当组织所有者对所有新仓库禁用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | 当组织所有者对所有新仓库启用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。                                                                                                                                         |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `dependency_graph` 类操作
+
+| 操作   | 描述                                                                                                                                                              |
+| ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | 当组织所有者对所有现有仓库禁用依赖项图时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | 当组织所有者对所有现有仓库启用依赖项图时触发。                                                                                                                                         |
+
+### `dependency_graph_new_repos` 类操作
+
+| 操作   | 描述                                                                                                                                                             |
+| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | 当组织所有者对所有新仓库禁用依赖项图时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `启用` | 当组织所有者对所有新仓库启用依赖项图时触发。                                                                                                                                         |
+{% endif %}
+
+### `discussion_post` 类操作
+
+| 操作        | 描述                                                                           |
+| --------- | ---------------------------------------------------------------------------- |
+| `update`  | 当[团队讨论帖子被编辑](/articles/managing-disruptive-comments/#editing-a-comment)时触发。  |
+| `destroy` | 当[团队讨论帖子被删除](/articles/managing-disruptive-comments/#deleting-a-comment)时触发。 |
+
+### `discussion_post_reply` 类操作
+
+| 操作        | 描述                                                                              |
+| --------- | ------------------------------------------------------------------------------- |
+| `update`  | 当[团队讨论帖子的回复被编辑](/articles/managing-disruptive-comments/#editing-a-comment)时触发。  |
+| `destroy` | 当[团队讨论帖子的回复被删除](/articles/managing-disruptive-comments/#deleting-a-comment)时触发。 |
+
+{% ifversion fpt or ghes or ghec %}
+### `enterprise` 类别操作
+
+{% data reusables.actions.actions-audit-events-for-enterprise %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `environment` 类别操作
+
+| 操作                      | 描述                                                                                   |
+| ----------------------- | ------------------------------------------------------------------------------------ |
+| `create_actions_secret` | 在环境中创建机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。   |
+| `delete`                | 当环境被删除时触发。 更多信息请参阅“[删除环境](/actions/reference/environments#deleting-an-environment)”。 |
+| `remove_actions_secret` | 从环境中删除机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。   |
+| `update_actions_secret` | 当环境中的机密更新时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。  |
+{% endif %}
+
+{% ifversion ghae %}
+### `external_group` category actions
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% endif %}
+
+{% ifversion ghae %}
+### `external_identity` category actions
+
+{% data reusables.saml.external-identity-audit-events %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `git` 类操作
+
+{% note %}
+
+**注：**要访问审核日志中的 Git 事件，必须使用审核日志 REST API。 审核日志 REST API 仅供 {% data variables.product.prodname_ghe_cloud %} 用户使用。 更多信息请参阅“[组织](/rest/reference/orgs#get-the-audit-log-for-an-organization)”。
+
+{% endnote %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+| 操作   | 描述           |
+| ---- | ------------ |
+| `克隆` | 当仓库被克隆时触发。   |
+| `获取` | 从仓库获取更改时触发。  |
+| `推送` | 将更改推送到仓库时触发。 |
+
+{% endif %}
+
+### `hook` 类操作
+
+| 操作               | 描述                                                 |
+| ---------------- | -------------------------------------------------- |
+| `create`         | 当[新挂钩被添加](/articles/creating-webhooks)到组织拥有的仓库时触发. |
+| `config_changed` | 当现有挂钩的配置发生更改时触发。                                   |
+| `destroy`        | 从仓库中删除现有挂钩时触发。                                     |
+| `events_changed` | 当挂钩上的事件发生更改时触发。                                    |
+
+### `integration_installation_request` 类操作
+
+| 操作       | 描述                                          |
+| -------- | ------------------------------------------- |
+| `create` | 当组织成员请求组织所有者安装集成以用于组织时触发。                   |
+| `close`  | 当安装集成以用于组织的请求被组织所有者批准或拒绝，或者被提出请求的组成成员取消时触发。 |
+
+### `ip_allow_list` 类操作
+
+| 操作                           | 描述                                                                       |
+| ---------------------------- | ------------------------------------------------------------------------ |
+| `启用`                         | 为组织启用 IP 允许列表时触发。                                                        |
+| `禁用`                         | 为组织禁用 IP 允许列表时触发。                                                        |
+| `enable_for_installed_apps`  | 为已安装的 {% data variables.product.prodname_github_apps %} 启用 IP 允许列表时触发。 |
+| `disable_for_installed_apps` | 为已安装的 {% data variables.product.prodname_github_apps %} 禁用 IP 允许列表时触发。 |
+
+### `ip_allow_list_entry` 类操作
+
+| 操作        | 描述                                                              |
+| --------- | --------------------------------------------------------------- |
+| `create`  | IP 地址添加到 IP 允许列表中时触发。                                           |
+| `update`  | Triggered when an IP address or its description was changed.    |
+| `destroy` | Triggered when an IP address was deleted from an IP allow list. |
+
+### `issue` 类操作
+
+| 操作        | 描述                                   |
+| --------- | ------------------------------------ |
+| `destroy` | 当组织所有者或仓库中具有管理员权限的人从组织拥有的仓库中删除议题时触发。 |
+
+{% ifversion fpt or ghec %}
+
+### `marketplace_agreement_signature` 类操作
+
+| 操作       | 描述                                                              |
+| -------- | --------------------------------------------------------------- |
+| `create` | 在签署 {% data variables.product.prodname_marketplace %} 开发者协议时触发。 |
+
+### `marketplace_listing` 类操作
+
+| 操作        | 描述                                                                   |
+| --------- | -------------------------------------------------------------------- |
+| `批准`      | 当您的列表被批准包含在 {% data variables.product.prodname_marketplace %} 中时触发。  |
+| `create`  | 当您在 {% data variables.product.prodname_marketplace %} 中为应用程序创建列表时触发。 |
+| `delist`  | 当您的列表从 {% data variables.product.prodname_marketplace %} 中被删除时触发。    |
+| `redraft` | 将您的列表被返回到草稿状态时触发。                                                    |
+| `reject`  | 当您的列表被拒绝包含在 {% data variables.product.prodname_marketplace %} 中时触发。  |
+
+{% endif %}
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+
+### `members_can_create_pages` 类操作
+
+更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。
+
+| 操作   | 描述                                                                   |
+|:---- |:-------------------------------------------------------------------- |
+| `启用` | 当组织所有者启用在组织中的仓库发布 {% data variables.product.prodname_pages %} 站点时触发。 |
+| `禁用` | 当组织所有者禁止在组织中的仓库发布 {% data variables.product.prodname_pages %} 站点时触发。 |
+
+{% endif %}
+
+### `org` 类操作
+
+| 操作                                                  | 描述                                                                                                                                                                                                                                                                                                                                                           |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `add_member`                                        | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_policy_selected_member_disabled` | 当企业所有者阻止为组织拥有的仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `advanced_security_policy_selected_member_enabled`  | 当企业所有者允许为组织拥有的仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %}
+| `audit_log_export`                                  | 组织管理员[创建组织审核日志导出](#exporting-the-audit-log)时触发。 如果导出包含查询，则日志将列出所使用的查询以及与该查询匹配的审核日志条目数量。                                                                                                                                                                                                                                                                      |
+| `block_user`                                        | 当组织所有者[阻止用户访问组织的仓库](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)时触发。                                                                                                                                                                                                                                               |
+| `cancel_invitation`                                 | 当组织邀请被撤销时触发的。                                                                                                                                                                                                                                                                                                                                                |{% endif %}{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                             | 为组织创建 {% data variables.product.prodname_actions %} 机密时触发。 更多信息请参阅“[为组织创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)”。{% endif %}                                                                                                                                                                             |{% ifversion fpt or ghec %}
+| `disable_oauth_app_restrictions`                    | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `disable_saml`                                      | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %}
+| `disable_member_team_creation_permission`           | 当组织所有者将团队创建限于所有者时触发。 更多信息请参阅“[设置组织中的团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”。 |{% ifversion not ghae %}
+| `disable_two_factor_requirement`                    | 当所有者对组织中的所有成员{% ifversion fpt or ghec %}、帐单管理员{% endif %} 和外部协作者禁用双重身份验证要求时触发。{% endif %}{% ifversion fpt or ghec %}
+| `enable_oauth_app_restrictions`                     | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `enable_saml`                                       | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %}
+| `enable_member_team_creation_permission`            | 当组织所有者允许成员创建团队时触发。 更多信息请参阅“[设置组织中的团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”。 |{% ifversion not ghae %}
+| `enable_two_factor_requirement`                     | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `invite_member`                                     | 当[新用户被邀请加入您的组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)时触发。                                                                                                                                                                                                                                        |
+| `oauth_app_access_approved`                         | 当所有者[授权组织访问 {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/) 时触发。                                                                                                                                                                                                                                   |
+| `oauth_app_access_denied`                           | 当所有者对组织[禁用先前批准的 {% data variables.product.prodname_oauth_app %} 权限](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)时触发。                                                                                                                                                                                                 |
+| `oauth_app_access_requested`                        | 当组织成员请求所有者对组织授予 {% data variables.product.prodname_oauth_app %} 权限时触发。{% endif %}
+| `register_self_hosted_runner`                       | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到组织](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)”。                                                                                                                                                                                                        |
+| `remove_actions_secret`                             | 当 {% data variables.product.prodname_actions %} 密码删除时触发。{% ifversion fpt or ghec %}
+| `remove_billing_manager`                            | 当[所有者从组织中删除帐单管理员](/articles/removing-a-billing-manager-from-your-organization/)，或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但帐单管理员未使用 2FA 或禁用 2FA 时触发。 
+{% endif %}
+| `remove_member`                                     | 当[所有者从组织中删除成员](/articles/removing-a-member-from-your-organization/)，{% ifversion not ghae %} 或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但组织成员未使用 2FA 或禁用 2FA 时触发{% endif %}。 当[组织成员从组织中删除自己](/articles/removing-yourself-from-an-organization/)时也会触发。                                                             |
+| `remove_outside_collaborator`                       | 当所有者从组织中删除外部协作者，{% ifversion not ghae %} 或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但外部协作者未使用 2FA 或禁用 2FA 时触发{% endif %}。                                                                                                                                                                                         |
+| `remove_self_hosted_runner`                         | 当自托管运行器被移除时触发。 更多信息请参阅“[从组织移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)”。                                                                                                                                                                                                                   |{% ifversion ghec %}
+| `revoke_external_identity`                          | 当组织所有者撤销成员的链接身份时触发。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。                                                                                                                     |
+| `revoke_sso_session`                                | 当组织所有者撤销成员的 SAML 会话时触发。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。                                                                                                                 |{% endif %}
+| `runner_group_created`                              | 在创建自托管运行器组时触发。 更多信息请参阅“[为组织创建自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)”。                                                                                                                                                                       |
+| `runner_group_removed`                              | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。                                                                                                                                                                                             |
+| `runner_group_updated`                              | 当自托管运行器组的配置改变时触发。 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。                                                                                                                                                                 |
+| `runner_group_runners_added`                        | 当自托管运行器添加到组时触发。 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。                                                                                                                                                                                        |
+| `runner_group_runner_removed`                       | 当 REST API 用于从组中删除自托管运行器时触发。 更多信息请参阅“[为组织从组中删除自托管运行器](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)”。                                                                                                                                                                                                                |
+| `runner_group_runners_updated`                      | 当运行器组成员列表更新时触发。 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`                         | 当运行器应用程序启动时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。                                                                                                                                            |
+| `self_hosted_runner_offline`                        | 当运行器应用程序停止时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`                        | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy`              | 为组织改变需要批准来自公共复刻的工作流程的设置时触发。 更多信息请参阅“[需要批准来自公共复刻的工作流程](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)”。{% endif %}
+| `set_actions_retention_limit`                       | 改变 {% data variables.product.prodname_actions %} 构件和日志的保留期时触发。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)”。{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`                      | 更改私有仓库复刻上的工作流程策略时触发。 更多信息请参阅“[为私有仓库复刻启用工作流程](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)”。{% endif %}{% ifversion fpt or ghec %}
+| `unblock_user`                                      | 当组织所有者[取消阻止用户访问组织](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)时触发。{% endif %}{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                             | 当 {% data variables.product.prodname_actions %} 密码更新时触发。{% endif %}
+| `update_new_repository_default_branch_setting`      | 当所有者更改组织中新仓库的默认分支名称时触发。 更多信息请参阅“[管理组织中仓库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”。                                                                                                                                                                                     |
+| `update_default_repository_permission`              | 当所有者更改组织成员的默认仓库权限级别时触发的。                                                                                                                                                                                                                                                                                                                                     |
+| `update_member`                                     | 当所有者将某人的角色从所有者更改为成员或者从成员更改为所有者时触发。                                                                                                                                                                                                                                                                                                                           |
+| `update_member_repository_creation_permission`      | 当所有者更改组织成员创建仓库的权限时触发。{% ifversion fpt or ghec %}
+| `update_saml_provider_settings`                     | 当组织的 SAML 提供程序设置被更新时触发。                                                                                                                                                                                                                                                                                                                                      |
+| `update_terms_of_service`                           | 当组织在标准服务条款和公司服务条款之间切换时触发。 更多信息请参阅“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。{% endif %}
+
+{% ifversion ghec %}
+### `org_credential_authorization` 类操作
+
+| 操作             | 描述                                                                                                                                                              |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grant`        | 当成员[授权用于 SAML 单点登录的凭据](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)时触发。                                                            |
+| `deauthorized` | 当成员[取消授权用于 SAML 单点登录的凭据](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)时触发。                                                          |
+| `revoke`       | 当所有者[撤销授权的凭据](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)时触发。 |
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghae or ghec %}
+### `organization_label` 类操作
+
+| 操作        | 描述         |
+| --------- | ---------- |
+| `create`  | 创建默认标签时触发。 |
+| `update`  | 编辑默认标签时触发。 |
+| `destroy` | 删除默认标签时触发。 |
+
+{% endif %}
+
+### `oauth_application` 类操作
+
+| 操作              | 描述                                                                |
+| --------------- | ----------------------------------------------------------------- |
+| `create`        | 在创建新 {% data variables.product.prodname_oauth_app %} 时触发。       |
+| `destroy`       | 当现有 {% data variables.product.prodname_oauth_app %} 被删除时触发。     |
+| `reset_secret`  | 当 {% data variables.product.prodname_oauth_app %} 的客户端密钥被重置时触发。 |
+| `revoke_tokens` | 当 {% data variables.product.prodname_oauth_app %} 的用户令牌被撤销时触发。  |
+| `转让`            | 当现有 {% data variables.product.prodname_oauth_app %} 被转让到新组织时触发。 |
+
+{% ifversion fpt or ghes > 3.0 or ghec %}
+### `packages` 类操作
+
+| 操作                          | 描述                                                                                                     |
+| --------------------------- | ------------------------------------------------------------------------------------------------------ |
+| `package_version_published` | 当软件包版本发布时触发。                                                                                           |
+| `package_version_deleted`   | 当特定软件包版本被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 |
+| `package_deleted`           | 在整个软件包被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。   |
+| `package_version_restored`  | 当特定软件包版本被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 |
+| `package_restored`          | 在整个软件包恢复时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。    |
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `payment_method` 类操作
+
+| 操作       | 描述                                |
+| -------- | --------------------------------- |
+| `create` | 在添加新的付款方式（例如新的信用卡或 PayPal 帐户）时触发。 |
+| `update` | 当现有付款方式被更新时触发。                    |
+
+{% endif %}
+
+### `profile_picture` 类操作
+| 操作     | 描述                |
+| ------ | ----------------- |
+| update | 在设置或更新组织的资料图片时触发。 |
+
+### `project` 类操作
+
+| 操作                       | 描述                                     |
+| ------------------------ | -------------------------------------- |
+| `create`                 | 在创建项目板时触发。                             |
+| `link`                   | 当仓库被链接到项目板时触发。                         |
+| `rename`                 | 当项目板被重命名时触发。                           |
+| `update`                 | 当项目板被更新时触发。                            |
+| `delete`                 | 在删除项目板时触发。                             |
+| `unlink`                 | 当仓库从项目板解除链接时触发。                        |
+| `update_org_permission`  | 当所有组织成员的基本级别权限被更改或删除时触发。               |
+| `update_team_permission` | 当团队的项目板权限级别被更改，或者在项目板中添加或删除团队时触发。      |
+| `update_user_permission` | 在项目板中添加或删除组织成员或外部协作者时，或者他们的权限级别被更改时触发。 |
+
+### `protected_branch` 类操作
+
+| 操作                                                    | 描述                                                                                    |
+| ----------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| `create`                                              | 在分支上启用分支保护时触发。                                                                        |
+| `destroy`                                             | 在分支上禁用分支保护时触发。                                                                        |
+| `update_admin_enforced`                               | 为仓库管理员实施分支保护时触发。                                                                      |
+| `update_require_code_owner_review`                    | 在分支上更新必需代码所有者审查的实施时触发。                                                                |
+| `dismiss_stale_reviews`                               | 在分支上更新忽略旧拉取请求的实施时触发。                                                                  |
+| `update_signature_requirement_enforcement_level`      | 在分支上更新必需提交签名的实施时触发。                                                                   |
+| `update_pull_request_reviews_enforcement_level`       | 在分支上更新必需拉取请求审查的实施时触发。 Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). |
+| `update_required_status_checks_enforcement_level`     | 在分支上更新必需状态检查的实施时触发。                                                                   |
+| `update_strict_required_status_checks_policy`         | 当分支在合并之前保持最新的要求被更改时触发。                                                                |
+| `rejected_ref_update`                                 | 当分支更新尝试被拒绝时触发。                                                                        |
+| `policy_override`                                     | 当仓库管理员重写分支保护要求时触发。{% ifversion fpt or ghes or ghae or ghec %}
+| `update_allow_force_pushes_enforcement_level`         | 对受保护分支启用或禁用强制推送时触发。                                                                   |
+| `update_allow_deletions_enforcement_level`            | 对受保护分支启用或禁用分支删除时触发。                                                                   |
+| `update_linear_history_requirement_enforcement_level` | 对受保护分支启用或禁用必要线性提交历史记录时触发。                                                             |
+{% endif %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+
+### `pull_request` 类操作
+
+| 操作                      | 描述                            |
+| ----------------------- | ----------------------------- |
+| `create`                | 在创建拉取请求时触发。                   |
+| `close`                 | 在未合并的情况下关闭拉取请求时触发。            |
+| `重新激活`                  | 当之前关闭的拉取请求重新打开时触发。            |
+| `合并`                    | 当拉取请求合并时触发。                   |
+| `indirect_merge`        | 当拉取请求被视为合并时触发，因为其提交被合并到目标分支中。 |
+| `ready_for_review`      | 当拉请求被标记为可供审核时触发。              |
+| `converted_to_draft`    | 当拉请求转换为草稿时触发。                 |
+| `create_review_request` | 当请求审核时触发。                     |
+| `remove_review_request` | 当审核请求被移除时触发。                  |
+
+### `pull_request_review` 类操作
+
+| 操作       | 描述         |
+| -------- | ---------- |
+| `提交`     | 在提交审核时触发。  |
+| `忽略`     | 当审核被忽略时触发。 |
+| `delete` | 当审核被删除时触发。 |
+
+### `pull_request_review_comment` 类操作
+
+| 操作       | 描述          |
+| -------- | ----------- |
+| `create` | 在添加审核评论时触发。 |
+| `update` | 在更改审核评论时触发。 |
+| `delete` | 在删除审核评论时触发。 |
+
+{% endif %}
+
+### `repo` 类操作
+
+| 操作                                     | 描述                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                               | 当用户[更改组织中仓库的可见性](/github/administering-a-repository/setting-repository-visibility)时触发。                                                                                                                                                                                                                                                                                                                                |
+| `actions_enabled`                      | 为仓库启用 {% data variables.product.prodname_actions %} 时触发。 可以使用用户界面查看。 当您使用 REST API 访问审计日志时，不包括此事件。 更多信息请参阅“[使用 REST API](#using-the-rest-api)”。                                                                                                                                                                                                                                                                       |
+| `add_member`                           | 当用户接受[邀请以获取仓库协作权限](/articles/inviting-collaborators-to-a-personal-repository)时触发。                                                                                                                                                                                                                                                                                                                                     |
+| `add_topic`                            | 当仓库管理员向仓库[添加主题](/articles/classifying-your-repository-with-topics)时触发。{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| `advanced_security_disabled`           | 当仓库管理员为仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。                                                                                                                                                                                                              |
+| `advanced_security_enabled`            | 当仓库管理员为仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %}
+| `archived`                             | 当仓库管理员[存档仓库](/articles/about-archiving-repositories)时触发。{% ifversion ghes %}
+| `config.disable_anonymous_git_access`  | 当公共仓库中[禁用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。                                                                                                                                                                                                                                                                                         |
+| `config.enable_anonymous_git_access`   | 当公共仓库中[启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。                                                                                                                                                                                                                                                                                         |
+| `config.lock_anonymous_git_access`     | 当仓库的[匿名 Git 读取权限设置被锁定](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。                                                                                                                                                                                                                                                                    |
+| `config.unlock_anonymous_git_access`   | 当仓库的[匿名 Git 读取权限设置被解锁](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。{% endif %}
+| `create`                               | 在[创建新仓库](/articles/creating-a-new-repository)时触发。{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret`                | 为仓库创建 {% data variables.product.prodname_actions %} 密码时触发。 更多信息请参阅“[为仓库创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。{% endif %}
+| `destroy`                              | 当[仓库被删除](/articles/deleting-a-repository)时触发。{% ifversion fpt or ghec %}
+| `禁用`                                   | 当仓库被禁用（例如，因[资金不足](/articles/unlocking-a-locked-account)）时触发。{% endif %}
+| `启用`                                   | 在重新启用仓库时触发。{% ifversion fpt or ghes or ghec %}
+| `remove_actions_secret`                | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。{% endif %}
+| `remove_member`                        | 从[仓库中删除用户的协作者身份](/articles/removing-a-collaborator-from-a-personal-repository)时触发。                                                                                                                                                                                                                                                                                                                                    |
+| `register_self_hosted_runner`          | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。                                                                                                                                                                                                                                                                    |
+| `remove_self_hosted_runner`            | 当自托管运行器被移除时触发。 更多信息请参阅“[从仓库移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)”。                                                                                                                                                                                                                                                                               |
+| `remove_topic`                         | 当仓库管理员从仓库中删除主题时触发。                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `rename`                               | 在[新仓库重命名](/articles/renaming-a-repository)时触发。{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `self_hosted_runner_online`            | 当运行器应用程序启动时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。                                                                                                                                                                                                     |
+| `self_hosted_runner_offline`           | 当运行器应用程序停止时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated`           | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | 改变需要批准来自公共复刻的工作流程的设置时触发。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)”。{% endif %}
+| `set_actions_retention_limit`          | 改变 {% data variables.product.prodname_actions %} 构件和日志的保留期时触发。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy`         | 更改私有仓库复刻上的工作流程策略时触发。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)”。{% endif %}
+| `转让`                                   | 当[仓库被转让](/articles/how-to-transfer-a-repository)时触发。                                                                                                                                                                                                                                                                                                                                                                  |
+| `transfer_start`                       | 在仓库转让即将发生时触发。                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `unarchived`                           | 当仓库管理员取消存档仓库时触发。{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret`                | 当 {% data variables.product.prodname_actions %} 密码更新时触发。{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `repository_advisory` 类操作
+
+| 操作                 | 描述                                                                                                                                                         |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `close`            | 当有人关闭安全通告时触发。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 |
+| `cve_request`      | 当有人从 {% data variables.product.prodname_dotcom %} 为安全通告草稿申请 CVE（通用漏洞披露）编号时触发。                                                                              |
+| `github_broadcast` | 当 {% data variables.product.prodname_dotcom %} 在 {% data variables.product.prodname_advisory_database %} 中公开安全通告时触发。                                     |
+| `github_withdraw`  | 当 {% data variables.product.prodname_dotcom %} 撤回错误发布的安全通告时触发。                                                                                             |
+| `已激活`              | 当有人打开安全通告草稿时触发。                                                                                                                                            |
+| `publish`          | 当有人发布安全通告时触发。                                                                                                                                              |
+| `重新激活`             | 当有人重新打开安全通告草稿时触发。                                                                                                                                          |
+| `update`           | 当有人编辑草稿或发布安全通告时触发。                                                                                                                                         |
+
+### `repository_content_analysis` 类操作
+
+| 操作   | 描述                                                                                                                           |
+| ---- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `启用` | 当组织所有者或对仓库有管理员权限的人[对私有仓库启用数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)时触发。 |
+| `禁用` | 当组织所有者或对仓库有管理员权限的人[对私有仓库禁用数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)时触发。 |
+
+{% endif %}{% ifversion fpt or ghec %}
+
+### `repository_dependency_graph` 类操作
+
+| 操作   | 描述                                                                                                                                                                       |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `禁用` | 当仓库所有者或对仓库拥有管理员权限的人对{% ifversion fpt or ghec %}私有{% endif %}仓库禁用依赖项图时触发。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 |
+| `启用` | 当仓库所有者或对仓库拥有管理员权限的人对{% ifversion fpt or ghec %}私有{% endif %}仓库启用依赖项图时触发。                                                                                                 |
+
+{% endif %}{% ifversion ghec or ghes or ghae %}
+### `repository_secret_scanning` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                                                         |
+| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `启用` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository.                                                                               |
+
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+### `repository_vulnerability_alert` 类操作
+
+| 操作       | 描述                                                                                                                                                                                                                                                                                            |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |
+| `忽略`     | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency.                                                                                                          |
+| `解决`     | 当对仓库具有写入权限的人推送更改以更新和解决项目依赖项中的漏洞时触发。                                                                                                                                                                                                                                                           |
+
+{% endif %}{% ifversion fpt or ghec %}
+### `repository_vulnerability_alerts` 类操作
+
+| 操作                       | 描述                                                                                                                                                                                                                                                                   |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `authorized_users_teams` | 当组织所有者或对仓库有管理员权限的人更新有权接收仓库中有漏洞依赖项 {% data variables.product.prodname_dependabot_alerts %} 的人员或团队列表时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 |
+| `禁用`                     | 当仓库所有者或对仓库有管理员权限的人禁用 {% data variables.product.prodname_dependabot_alerts %} 时触发。                                                                                                                                                                                  |
+| `启用`                     | 当仓库所有者或对仓库有管理员权限的人启用 {% data variables.product.prodname_dependabot_alerts %} 时触发。                                                                                                                                                                                  |
+
+{% endif %}{% ifversion ghec %}
+### `role` category actions
+| 操作        | 描述                                                                                                                                                                                                                                                                                              |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`  | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."     |
+| `destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."          |
+| `update`  | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." |
+
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+### `secret_scanning` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                            |
+| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `启用` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.                                                                               |
+
+### `secret_scanning_new_repos` 类操作
+
+| 操作   | 描述                                                                                                                                                                                                                      |
+| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `禁用` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `启用` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.                                                                               |
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `sponsors` 类操作
+
+| 操作                                            | 描述                                                                                                                                                                                                                                        |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | 启用或禁用自定义金额时或更改建议的自定义金额时触发（请参阅“[管理您的赞助级别](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                             |
+| `repo_funding_links_file_action`              | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                         |
+| `sponsor_sponsorship_cancel`                  | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                               |
+| `sponsor_sponsorship_create`                  | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                            |
+| `sponsor_sponsorship_payment_complete`        | 当您赞助一个帐户并且您的付款已经处理完毕后触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                              |
+| `sponsor_sponsorship_preference_change`       | 当您更改是否接收被赞助帐户的电子邮件更新时触发（请参阅“[管理赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”）                                                                                                                             |
+| `sponsor_sponsorship_tier_change`             | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                |
+| `sponsored_developer_approve`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”）     |
+| `sponsored_developer_create`                  | 当您的 {% data variables.product.prodname_sponsors %} 帐户创建时触发（请参阅“<[为您的组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”）     |
+| `sponsored_developer_disable`                 | 帐户 {% data variables.product.prodname_sponsors %} 禁用时触发                                                                                                                                                                                   |
+| `sponsored_developer_redraft`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户从已批准状态恢复为草稿状态时触发                                                                                                                                                                     |
+| `sponsored_developer_profile_update`          | 在编辑您的赞助组织资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”）                                             |
+| `sponsored_developer_request_approval`        | 提交您对 {% data variables.product.prodname_sponsors %} 的申请以供审批时触发（请参阅“[为您的组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”）  |
+| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[管理赞助等级](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                   |
+| `sponsored_developer_update_newsletter_send`  | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)”）                                                                                                                        |
+| `waitlist_invite_sponsored_developer`         | 当您从等候名单被邀请加入 {% data variables.product.prodname_sponsors %} 时触发（请参阅“[为您的组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”） |
+| `waitlist_join`                               | 当您加入成为赞助组织的等候名单时触发（请参阅“[为您的组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”）                                              |
+{% endif %}
+
+### `team` 类操作
+
+| 操作                        | 描述                                                                                                                                                                                                                                                               |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member`              | 当组织成员被[添加到团队](/articles/adding-organization-members-to-a-team)时触发。                                                                                                                                                                                               |
+| `add_repository`          | 当团队被授予控制仓库的权限时触发。                                                                                                                                                                                                                                                |
+| `change_parent_team`      | 在创建子团队或[更改子团队的父级](/articles/moving-a-team-in-your-organization-s-hierarchy)时触发。                                                                                                                                                                                  |
+| `change_privacy`          | 当团队的隐私级别发生更改时触发。                                                                                                                                                                                                                                                 |
+| `create`                  | 在创建新团队时触发。                                                                                                                                                                                                                                                       |
+| `demote_maintainer`       | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."  |
+| `destroy`                 | 从组织中删除团队时触发。                                                                                                                                                                                                                                                     |
+| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." |
+| `remove_member`           | [从团队中删除组织成员](/articles/removing-organization-members-from-a-team)时触发。                                                                                                                                                                                            |
+| `remove_repository`       | 当仓库不再受团队控制时触发。                                                                                                                                                                                                                                                   |
+
+### `team_discussions` 类操作
+
+| 操作   | 描述                                                                                                    |
+| ---- | ----------------------------------------------------------------------------------------------------- |
+| `禁用` | 当组织所有者对组织禁用团队讨论时触发。 更多信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”。 |
+| `启用` | 当组织所有者对组织启用团队讨论时触发。                                                                                   |
+
+{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### `workflows` 类操作
+
+{% data reusables.actions.actions-audit-events-workflow %}
+{% endif %}
+## 延伸阅读
+
+- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
new file mode 100644
index 0000000000..bc1b0317b2
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md
@@ -0,0 +1,31 @@
+---
+title: 审查组织安装的集成
+intro: 您可以审查组织安装的集成的权限级别，并配置每个集成对组织仓库的访问权限。
+redirect_from:
+  - /articles/reviewing-your-organization-s-installed-integrations
+  - /articles/reviewing-your-organizations-installed-integrations
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations
+  - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 审核已安装的集成
+---
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**.
+{% elsif ghae or ghes < 3.4 %}
+1. 在左侧边栏中，单击 **Installed {% data variables.product.prodname_github_apps %}s（安装的 GitHub 应用程序）**。 ![组织设置边栏中安装的 {% data variables.product.prodname_github_apps %}选项卡](/assets/images/help/organizations/org-settings-installed-github-apps.png)
+{% endif %}
+2. 在您要审查的 {% data variables.product.prodname_github_app %} 旁边，单击 **Configure（配置）**。 ![配置按钮](/assets/images/help/organizations/configure-installed-integration-button.png)
+6. 审查 {% data variables.product.prodname_github_app %} 的权限和仓库访问权限。 ![授予 {% data variables.product.prodname_github_app %}所有仓库或特定仓库访问权限的选项](/assets/images/help/organizations/toggle-integration-repo-access.png)
+    - 要授予 {% data variables.product.prodname_github_app %}所有组织仓库的访问权限，请选择 **All repositories（所有仓库）**。
+    - 要选择特定仓库授予应用程序的访问权限，请选择 **Only select repositories（仅选择仓库）**，然后输入仓库名称。
+7. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
new file mode 100644
index 0000000000..df495a0d4f
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -0,0 +1,17 @@
+---
+title: Managing two-factor authentication for your organization
+shortTitle: Manage 2FA
+intro: You can view whether users with access to your organization have two-factor authentication (2FA) enabled and require 2FA.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /preparing-to-require-two-factor-authentication-in-your-organization
+  - /requiring-two-factor-authentication-in-your-organization
+---
+
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..b3d0fdb2ca
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: 准备在组织中要求双重身份验证
+intro: 在要求双重身份验证 (2FA) 之前，您可以向用户通知即将发生的更改，并验证谁已使用 2FA。
+redirect_from:
+  - /articles/preparing-to-require-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 准备需要 2FA
+---
+
+如果您的组织中需要 2FA，建议至少提前一周通知{% ifversion fpt or ghec %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}。
+
+需要对您的组织使用双重身份验证时，不使用 2FA 的成员、外部协作者和帐单管理员（包括自动程序帐户）将从组织中删除，并且失去访问其仓库的权限。 他们还会失去对组织私有仓库的复刻的访问权限。
+
+在组织中要求 2FA 之前，建议：
+  - 在个人帐户上[启用 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/)
+  - 要求组织中的人员为其帐户设置 2FA
+  - 查看[组织中的用户是否启用 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/)
+  - 提醒用户：2FA 一旦启用，没有 2FA 的用户会自动从组织中删除
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..196d51f2f0
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: 您的组织中需要双重身份验证
+intro: '组织所有者可以要求{% ifversion fpt or ghec %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}为其个人帐户启用双重身份验证，从而使恶意行为者更难以访问组织的仓库和设置。'
+redirect_from:
+  - /articles/requiring-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 需要 2FA
+---
+
+## 关于组织的双重身份验证
+
+{% data reusables.two_fa.about-2fa %} 您可以要求组织中的所有{% ifversion fpt or ghec %}成员、外部协作者和帐单管理员{% else %}成员和外部协作者{% endif %}在 {% data variables.product.product_name %} 上启用双重身份验证。 有关双重身份验证的更多信息，请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。
+
+{% ifversion fpt or ghec %}
+
+您还可以要求企业中的组织使用双重身份验证。 更多信息请参阅“[在企业中实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)”。
+
+{% endif %}
+
+{% warning %}
+
+**警告：**
+
+- 需要对您的组织使用双重身份验证时，不使用 2FA 的{% ifversion fpt or ghec %}成员、外部协作者和帐单管理员{% else %}成员和外部协作者{% endif %}（包括自动程序帐户）将从组织中删除，并且失去访问其仓库的权限。 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以[恢复其访问权限和设置](/articles/reinstating-a-former-member-of-your-organization)。
+- 如果组织所有者、成员{% ifversion fpt or ghec %}、帐单管理员{% endif %}或外部协作者在您启用所需的双重身份验证后为其个人帐户禁用 2FA，则系统会自动将其从组织中删除。
+- 如果您是某个要求双重身份验证的组织的唯一所有者，则在不为组织禁用双重身份验证要求的情况下，您将无法为个人帐户禁用双重身份验证。
+
+{% endwarning %}
+
+{% data reusables.two_fa.auth_methods_2fa %}
+
+## 基本要求
+
+在要求{% ifversion fpt or ghec %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}使用双重身份验证之前，您必须对 {% data variables.product.product_name %} 上的帐户启用双重身份验证。 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。
+
+在您需要使用双重身份验证之前，我们建议您通知{% ifversion fpt or ghec %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}，并要求他们为其帐户设置 2FA。 您可以查看成员和外部协作者是否已经使用 2FA。 更多信息请参阅“[查看组织中的用户是否已启用 2FA](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)”。
+
+## 您的组织中需要双重身份验证
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+{% ifversion fpt or ghec %}
+8. 如果从组织中删除了任何成员或外部协作者，我们建议向他们发送邀请，以恢复其以前对组织的权限和访问权限。 他们必须启用双重身份验证，然后才能接受您的邀请。
+{% endif %}
+
+## 查看从您的组织中删除的人员
+
+要查看在您要求双重身份验证时因为不合规而被从组织中自动删除的人员，您可以对从组织中删除的人员[搜索组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)。 审核日志事件将显示是否因为 2FA 不合规而删除该人员。
+
+![显示因 2FA 不合规而删除的用户的审核日志事件](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+4. 输入您的搜索查询。 要搜索：
+    - 删除的组织成员，请在搜索查询中使用 `action:org.remove_member`
+    - 删除的外部协作者，请在搜索查询中使用 `action:org.remove_outside_collaborator`{% ifversion fpt or ghec %}
+    - 删除的帐单管理员，请在搜索查询中使用 `action:org.remove_billing_manager`{% endif %}
+
+ 您还可以在搜索中使用[时间范围](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action)查看从组织中删除的人员。
+
+## 帮助被删除的成员和外部协作者重新加入您的组织
+
+如果在您启用双重身份验证使用要求时有任何成员或外部协作者被从组织中删除，他们将收到通知他们已被删除的电子邮件。 他们应当为个人帐户启用双重身份验证，并联系组织所有者来请求您的组织的访问权限。
+
+## 延伸阅读
+
+- “[查看组织中的用户是否已启用 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)”
+- “[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa)”
+- “[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”
+- “[恢复前外部协作者对组织的访问权限](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)”
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
new file mode 100644
index 0000000000..22328f419b
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -0,0 +1,33 @@
+---
+title: 查看组织中的用户是否已启用 2FA
+intro: 您可以查看哪些组织所有者、成员和外部协作者已启用双因素身份验证。
+redirect_from:
+  - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View 2FA usage
+---
+
+{% note %}
+
+**注：**您可以要求所有成员{% ifversion fpt or ghec %}（包括组织中的所有者、帐单管理员和{% else %}{% endif %} 外部协作者）均启用双因素身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)”。
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. 要查看已启用或已禁用双因素身份验证的组织成员（包括组织所有者），在右侧单击 **2FA**，然后选择 **Enabled（启用）**或 **Disabled（禁用）**。 ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png)
+5. 要查看组织中的外部协作者，在“People（人员）”选项卡下，单击 **Outside collaborators（外部协作者）**。 ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png)
+6. 要查看哪些外部协作者已启用或已禁用双因素身份验证，在右侧单击 **2FA**，然后选择 **Enabled（启用）**或 **Disabled（禁用）**。 ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
+
+## 延伸阅读
+
+- “[查看组织中人员的角色](/articles/viewing-people-s-roles-in-an-organization)”
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index 444020bc3e..cbffbca64c 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -40,8 +40,8 @@ Before you can add someone as an outside collaborator on a repository, the perso
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. 在“Choose a role（选择角色）”下，选择要授予此人的权限，然后单击 **Add NAME to REPOSITORY（将姓名添加到仓库）**。 ![为此人选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 260f64f326..9c96b97417 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -28,9 +28,13 @@ permissions: People with admin access to a repository can manage access to the r
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png)
+1. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. ![为团队或人员选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
 ## 管理个人对组织仓库的访问
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 447d4ccc7c..d2b3061811 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -78,6 +78,10 @@ shortTitle: 禁用或限制操作
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+{% ifversion ghec or ghae or ghes %}If a policy is disabled for an enterprise, it cannot be enabled for organizations.{% endif %} If a policy is disabled for an organization, it cannot be enabled for repositories. If an organization enables a policy, the policy can be disabled for individual repositories.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 ### 为组织配置私有复刻策略
 
 {% data reusables.profile.access_org %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
index 12c4c2956f..1e714b59e6 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -24,10 +24,13 @@ shortTitle: 禁用项目板
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-4. 决定是否禁用组织范围的项目板，禁用组织中的仓库项目板，或两者均禁用。 然后，在“项目”（项目）下：
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+{% endif %}
+1. 决定是否禁用组织范围的项目板，禁用组织中的仓库项目板，或两者均禁用。 然后，在“项目”（项目）下：
     - 要禁用组织范围的项目板，请取消选择 **Enable projects for the organization（启用组织的项目）**。
     - 要在组织中禁用仓库项目板，请取消选择 **Enable projects for all repositories（启用所有仓库的项目）**。 ![用于禁用单个组织或单个组织所有仓库的项目的复选框](/assets/images/help/projects/disable-org-projects-checkbox.png)
-5. 单击 **Save（保存）**。
+1. 单击 **Save（保存）**。
 
 {% data reusables.organizations.disable_project_board_results %}
 
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
index b08abf51fe..34feae56fb 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -10,14 +10,21 @@ versions:
 shortTitle: 集成 Jira
 ---
 
+{% ifversion ghes > 3.3 or ghae-issue-5658 %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**. ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. 单击 **New OAuth App（新建 OAuth 应用程序）**。
+{% elsif ghes < 3.4 or ghae %}
 {% data reusables.user_settings.access_settings %}
-2. 在左侧边栏的 **Organization settings（组织设置）**下，单击组织的名称。 ![侧边栏组织名称](/assets/images/help/settings/organization-settings-from-sidebar.png)
-3. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth applications（OAuth 应用程序）**。 ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png)
-4. 单击 **Register a new application（注册新应用程序）**。
-5. 在 **Application name（应用程序名称）**下输入 "Jira"。
-6. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。
-7. 在 **Authorization callback URL（授权回叫 URL）**下，输入 Jira 实例的完整 URL。
-8. 单击 **Register application（注册应用程序）**。 ![注册应用程序按钮](/assets/images/help/oauth/register-application-button.png)
+1. 在左侧边栏的 **Organization settings（组织设置）**下，单击组织的名称。 ![侧边栏组织名称](/assets/images/help/settings/organization-settings-from-sidebar.png)
+1. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth applications（OAuth 应用程序）**。 ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. 单击 **Register a new application（注册新应用程序）**。
+{% endif %}
+1. 在 **Application name（应用程序名称）**下输入 "Jira"。
+2. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。
+3. 在 **Authorization callback URL（授权回叫 URL）**下，输入 Jira 实例的完整 URL。
+4. 单击 **Register application（注册应用程序）**。 ![注册应用程序按钮](/assets/images/help/oauth/register-application-button.png)
 9. 在 **Organization owned applications（组织拥有的应用程序）**下，记下 "Client ID"（客户 ID）和 "Client Secret"（客户端密钥）值。 ![客户端 ID 和客户端密码](/assets/images/help/oauth/client-id-and-secret.png)
 {% data reusables.user_settings.jira_help_docs %}
 
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index e2ddc26111..a5c339d586 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -24,14 +24,13 @@ shortTitle: 管理预定提醒
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.slack-channel %}
 {% data reusables.reminders.days-dropdown %}
 {% data reusables.reminders.times-dropdowns %}
 {% data reusables.reminders.tracked-repos %}
-11. 在“Filter by team assigned to review code（按分配给审查代码的团队过滤）”下，单击 **Add a team（添加团队）**下拉列表并选择一个或多个团队。 您最多可以添加 100 个团队。 如果您选择的团队无法访问上面选择的“跟踪的仓库”，您将无法创建预定提醒。 ![添加团队下拉菜单](/assets/images/help/organizations/scheduled-reminders-add-teams.png)
+1.  在“Filter by team assigned to review code（按分配给审查代码的团队过滤）”下，单击 **Add a team（添加团队）**下拉列表并选择一个或多个团队。 您最多可以添加 100 个团队。 如果您选择的团队无法访问上面选择的“跟踪的仓库”，您将无法创建预定提醒。 ![添加团队下拉菜单](/assets/images/help/organizations/scheduled-reminders-add-teams.png)
 {% data reusables.reminders.ignore-drafts %}
 {% data reusables.reminders.no-review-requests %}
 {% data reusables.reminders.author-reviews %}
@@ -47,7 +46,6 @@ shortTitle: 管理预定提醒
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
@@ -56,7 +54,6 @@ shortTitle: 管理预定提醒
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 632584be9e..2273347c3a 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -23,6 +23,7 @@ shortTitle: 管理复刻策略
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index f89933d370..6440072c1d 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -63,3 +63,7 @@ shortTitle: 添加帐单管理员
 {% data reusables.organizations.billing-settings %}
 1. 在“Billing management（帐单管理）”下的“Billing managers（帐单管理员）”旁边，单击 **Add（添加）**。 ![邀请帐单管理员](/assets/images/help/billing/settings_billing_managers_list.png)
 6. 输入您要添加的人员的用户名或电子邮件地址，然后单击 **Send invitation（发送邀请）**。 ![邀请帐单管理员页面](/assets/images/help/billing/billing_manager_invite.png)
+
+## 延伸阅读
+
+- "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index 66fbcad27b..1d667d9e3c 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -90,6 +90,8 @@ You can only choose an additional permission if it's not already included in the
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
 - **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts.
+- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}.
+- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}.
 - **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts.
 
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index aeda1e0ef7..0ea73b302d 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -31,24 +31,11 @@ Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for
 
 ## 在 Okta 中添加 {% data variables.product.prodname_ghe_cloud %} 应用程序
 
-{% data reusables.saml.okta-sign-into-your-account %}
-1. Navigate to the [Github Enterprise Cloud - Organization](https://www.okta.com/integrations/github-enterprise-cloud-organization) application in the Okta Integration Network and click **Add Integration**.
-1. （可选）在“Application label（应用程序标签）”右边输入应用程序的描述性名称。
-1. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. 例如，如果组织的 URL 是 https://github.com/octo-org，则组织名称为 `octo-org`。
-1. 单击 **Done（完成）**。
-
-## 启用和测试 SAML SSO
-
-{% data reusables.saml.okta-sign-into-your-account %}
-{% data reusables.saml.okta-dashboard-click-applications %}
-{% data reusables.saml.okta-applications-click-ghec-application-label %}
-{% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
 1. 按照“如何配置 SAML 2.0”指南，使用登录 URL、发行机构 URL 和公共证书在 {% data variables.product.prodname_dotcom %} 上启用并测试 SAML SSO。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)”。
 
 ## 在 Okta 中使用 SCIM 配置访问配置
-
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.okta-provisioning-tab %}
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index b285cb7e87..a9d17a0738 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -57,7 +57,11 @@ When code owners are automatically requested for review, the team is still remov
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
 1. Select **Only notify requested team members.** ![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
 1. 单击 **Save changes（保存更改）**。
 {% endif %}
@@ -67,7 +71,11 @@ When code owners are automatically requested for review, the team is still remov
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
 1. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
 1. 选择 **Enable auto assignment（启用自动分配）**。 ![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
 1. 在“How many team members should be assigned to review?（应分配多少团队成员进行审查？）”下，使用下拉菜单选择多个要分配给每个拉取请求的审查者。 ![审查者人数下拉列表](/assets/images/help/teams/review-assignment-number.png)
 1. 在“Routing algorithm（路由算法）”下，使用下拉菜单选择要使用的算法。 更多信息请参阅“[路由算法](#routing-algorithms)”。 ![路由算法下拉列表](/assets/images/help/teams/review-assignment-algorithm.png)
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
index 96b3213f09..e79ec505e0 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
@@ -27,7 +27,6 @@ shortTitle: 预定提醒
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.add-reminder %}
 {% data reusables.reminders.authorize-slack %}
 {% data reusables.reminders.slack-channel %}
@@ -51,7 +50,6 @@ shortTitle: 预定提醒
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.edit-existing %}
 {% data reusables.reminders.edit-page %}
 {% data reusables.reminders.update-buttons %}
@@ -62,7 +60,6 @@ shortTitle: 预定提醒
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% data reusables.reminders.scheduled-reminders %}
-![预定提醒按钮](/assets/images/help/teams/scheduled-reminders-teams.png)
 {% data reusables.reminders.delete %}
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index 02c71d43f7..f0094c8972 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -176,7 +176,7 @@ To review who can delete a package version, see "[Required permissions to delete
 - 您在删除后 30 天内恢复包。
 - 相同的包名称空间和版本仍然可用，并且不重复用于新包。
 
-例如，如果您删除了名为 `octo-package` 且范围为 repo `octo-repo-owner/octo-repo` 的 rubygem 包，则您仅在包名称空间 `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` 仍然可用且 30 天未过时才可恢复包。
+For example, if you have a deleted RubyGems package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
 
 {% ifversion fpt or ghec %}
 To restore a deleted package, you must also meet one of these permission requirements:
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
index 22d46ba47a..d801f5049b 100644
--- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -23,7 +23,7 @@ shortTitle: RubyGems registry
 
 ## Prerequisites
 
-- You must have rubygems 2.4.1 or higher. To find your rubygems version:
+- You must have RubyGems 2.4.1 or higher. To find your RubyGems version:
 
   ```shell
   $ gem --version
@@ -86,7 +86,7 @@ If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this exa
 
 ```
 
-To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
 
 ```shell
 $ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index 8c7a2b3524..fc37d655fb 100644
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -23,7 +23,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
 ## Verifying a domain for your user site
 
 {% data reusables.user_settings.access_settings %}
-1. 在左侧边栏中，单击 **Pages（页面）**。 ![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
@@ -37,7 +37,7 @@ Organization owners can verify custom domains for their organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. 在左侧边栏中，单击 **Pages（页面）**。 ![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
 {% data reusables.pages.settings-verify-domain-setup %}
 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
   ```
diff --git a/translations/zh-CN/content/pages/quickstart.md b/translations/zh-CN/content/pages/quickstart.md
index bd8068c3a2..12d738d1bb 100644
--- a/translations/zh-CN/content/pages/quickstart.md
+++ b/translations/zh-CN/content/pages/quickstart.md
@@ -25,12 +25,12 @@ This guide will lead you through creating a user site at `username.github.io`.
 {% data reusables.repositories.create_new %}
 1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`. ![Repository name field](/assets/images/help/pages/create-repository-name-pages.png)
 {% data reusables.repositories.sidebar-settings %}
-1. 在左侧边栏中，单击 **Pages（页面）**。 ![左侧边栏中的页面选项卡](/assets/images/help/pages/pages-tab.png)
+{% data reusables.pages.sidebar-pages %}
 1. Click **Choose a theme**. ![选择主题按钮](/assets/images/help/pages/choose-theme.png)
-1. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. ![主题选项和选择主题按钮](/assets/images/help/pages/select-theme.png)
-1. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
-1. When you are done editing the file, click **Commit changes**.
-1. Visit `username.github.io` to view your new website. **注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 20 分钟才会发布。
+2. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. ![主题选项和选择主题按钮](/assets/images/help/pages/select-theme.png)
+3. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
+4. When you are done editing the file, click **Commit changes**.
+5. Visit `username.github.io` to view your new website. **注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 20 分钟才会发布。
 
 ## Changing the title and description
 
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index 69eeeb7aea..81b982920e 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -35,7 +35,7 @@ topics:
 
 _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
 
-组织所有者和能够推送到仓库的用户可使用 {% data variables.product.product_name %} 的 API 创建检查和状态。 更多信息请参阅“[检查](/rest/reference/checks)”和“[状态](/rest/reference/repos#statuses)”。
+组织所有者和能够推送到仓库的用户可使用 {% data variables.product.product_name %} 的 API 创建检查和状态。 更多信息请参阅“[检查](/rest/reference/checks)”和“[状态](/rest/reference/commits#commit-statuses)”。
 
 ## 检查
 
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index 47571710d4..249ceb2fa2 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -162,6 +162,7 @@ gh pr create --web
 ## 延伸阅读
 
 - "[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)"
 - “[更改拉取请求的基本分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)”
 - “[从侧边栏向项目板添加议题和拉取请求](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)”
 - "[关于使用查询参数自动化议题和拉取请求](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index d9f18c560f..a9adb5e672 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -22,6 +22,7 @@ children:
   - /using-query-parameters-to-create-a-pull-request
   - /changing-the-stage-of-a-pull-request
   - /requesting-a-pull-request-review
+  - /keeping-your-pull-request-in-sync-with-the-base-branch
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
 shortTitle: 提议更改
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
new file mode 100644
index 0000000000..0366b951bd
--- /dev/null
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
@@ -0,0 +1,53 @@
+---
+title: Keeping your pull request in sync with the base branch
+intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.'
+permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Update the head branch
+---
+
+## About keeping your pull request in sync
+
+Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging.
+
+You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true:
+
+* There are no merge conflicts between the pull request branch and the base branch.
+* The pull request branch is not up to date with the base branch.
+* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %} or the setting to always suggest updating branches is enabled{% endif %}.
+
+For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}" and "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}."
+
+If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)."
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created.
+{% else %}
+Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request.
+{% endif %}
+
+## Updating your pull request branch
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull requests" list, click the pull request you'd like to update.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}
+1. In the merge section near the bottom of the page, you can:
+   - Click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png)
+   - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch. ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png)
+{% else %}
+1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge. ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch.png)
+{% endif %}
+
+## 延伸阅读
+
+- "[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)"
+- "[提交更改至创建自复刻的拉取请求分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
index 489b1c7a00..ddd27b8037 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
@@ -19,4 +19,4 @@ shortTitle: 配置提交变基
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 在“Merge（合并）”按钮下，选择 **Allow rebase merging（允许变基合并）**。 这将允许贡献者通过将其个人提交变基到基本分支来合并拉取请求。 如果您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求变基提交](/assets/images/help/repository/pr-merge-rebase.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. 这将允许贡献者通过将其个人提交变基到基本分支来合并拉取请求。 如果您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求变基提交](/assets/images/help/repository/pr-merge-rebase.png)
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
index 6d95de8d4b..c206a26832 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -21,8 +21,8 @@ shortTitle: 配置提交压缩
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 在“Merge（合并）”按钮下，可选择 **Allow merge commits（允许合并提交）**。 这将允许贡献者合并具有完整提交历史记录的拉取请求。 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
-4. 在“Merge（合并）”按钮下，选择 **Allow squash merging（允许压缩合并）**。 这将允许贡献者通过将所有提交压缩到单个提交中来合并拉取请求。 如果除了 **Allow squash merging（允许压缩合并）**之外，您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求压缩提交](/assets/images/help/repository/pr-merge-squash.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. 这将允许贡献者合并具有完整提交历史记录的拉取请求。 ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png)
+4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. 这将允许贡献者通过将所有提交压缩到单个提交中来合并拉取请求。 如果除了 **Allow squash merging（允许压缩合并）**之外，您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求压缩提交](/assets/images/help/repository/pr-merge-squash.png)
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
index 3200ff0be4..141f209e8e 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -16,6 +16,7 @@ children:
   - /configuring-commit-squashing-for-pull-requests
   - /configuring-commit-rebasing-for-pull-requests
   - /using-a-merge-queue
+  - /managing-suggestions-to-update-pull-request-branches
   - /managing-auto-merge-for-pull-requests-in-your-repository
   - /managing-the-automatic-deletion-of-branches
 shortTitle: 配置 PR 合并
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 6a27eccd45..02ecdc499b 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -26,4 +26,4 @@ shortTitle: 管理自动合并
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. 在“Merge button（合并按钮）”下，选择或取消选择 **Allow auto-merge（允许自动合并）**。 ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
+1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**. ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
new file mode 100644
index 0000000000..a724a1302b
--- /dev/null
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -0,0 +1,23 @@
+---
+title: Managing suggestions to update pull request branches
+intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+versions:
+  fpt: '*'
+  ghes: '> 3.4'
+  ghae: issue-6069
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage branch updates
+permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
+---
+
+## About suggestions to update a pull request branch
+
+If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+## Managing suggestions to update a pull request branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**. ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
index caf7df9159..9043262f77 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
@@ -19,7 +19,7 @@ shortTitle: 自动删除分支
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 在“Merge（合并）”按钮下，选择或取消选择 **Automatically delete head branches（自动删除头部分支）**。 ![启用或禁用分支自动删除的复选框](/assets/images/help/repository/automatically-delete-branches.png)
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or unselect **Automatically delete head branches**. ![启用或禁用分支自动删除的复选框](/assets/images/help/repository/automatically-delete-branches.png)
 
 ## 延伸阅读
 - "[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index c23e489ed8..feae43c962 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -84,7 +84,7 @@ remote: error: Changes have been requested.
 
 必需状态检查确保在协作者可以对受保护分支进行更改前，所有必需的 CI 测试都已通过。 更多信息请参阅“[配置受保护分支](/articles/configuring-protected-branches/)”和“[启用必需状态检查](/articles/enabling-required-status-checks)”。 更多信息请参阅“[关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks)”。
 
-必须配置仓库使用状态 API 后才可启用必需状态检查。 更多信息请参阅 REST 文档中的“[仓库](/rest/reference/repos#statuses)”。
+必须配置仓库使用状态 API 后才可启用必需状态检查。 更多信息请参阅 REST 文档中的“[仓库](/rest/reference/commits#commit-statuses)”。
 
 启用必需状态检查后，必须通过所有必需状态检查，协作者才能将更改合并到受保护分支。 所有必需状态检查通过后，必须将任何提交推送到另一个分支，然后合并或直接推送到受保护分支。
 
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 5b82ec66c2..965b635b8e 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -52,7 +52,8 @@ Prerequisites for repository transfers:
   $ git remote set-url origin <em>new_url</em>
   ```
 
-- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
+- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 2e4f77e92f..bfc685a54e 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -51,6 +51,8 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to
 CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用大多数规则的模式，但有[一些例外](#syntax-exceptions)。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
 
 如果 CODEOWNERS 文件中的任何行包含无效语法，则该文件将不会被检测并且不会用于请求审查。
+
+CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 ### CODEOWNERS 文件示例
 ```
 # This is a comment.
@@ -98,6 +100,10 @@ apps/ @octocat
 # subdirectories.
 /docs/ @doctocat
 
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
 # In this example, @octocat owns any file in the `/apps` 
 # directory in the root of your repository except for the `/apps/github` 
 # subdirectory, as its owners are left empty.
@@ -113,21 +119,6 @@ gitignore 文件有一些语法规则在 CODEOWNERS 文件中不起作用：
 ## CODEOWNERS and branch protection
 Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)”。
 
-### CODEOWNERS 文件示例
-```
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat.
-/apps/ @doctocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from @doctocat or @octocat.
-/apps/ @doctocat @octocat
-
-# In this example, any change inside the `/apps` directory
-# will require approval from a member of the @example-org/content team.
-/apps/ @example-org/content-team
-```
-
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 03d2328d39..2236315e27 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -87,6 +87,10 @@ You can configure this behavior for a repository using the procedure below. 修
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
+If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
+
+{% data reusables.github-actions.private-repository-forks-options %}
+
 ### 为仓库配置私有复刻策略
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -99,7 +103,7 @@ You can configure this behavior for a repository using the procedure below. 修
 
 {% data reusables.github-actions.workflow-permissions-intro %}
 
-默认权限也可以在组织设置中配置。 如果在组织设置中选择了更受限制的默认值，则在仓库设置中自动选择相同的选项，并禁用许可的选项。
+The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
 
 {% data reusables.github-actions.workflow-permissions-modifying %}
 
@@ -137,11 +141,11 @@ You can configure whether {% if internal-actions%}actions and {% endif %}workflo
 
 ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
 
-您可以为仓库中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。
+You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-您还可以为工作流程创建的特定构件自定义保留期。 更多信息请参阅“[设置构件的保留期](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)”。
+You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
 
 ## 设置仓库的保留期
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
index 5f1db6a869..f887726845 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -22,8 +22,12 @@ Anyone with admin permissions to a repository can configure autolink references
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. 在左侧边栏中，单击 **Autolink references（自动链接引用）**。 ![左侧边栏中的自动链接引用选项卡](/assets/images/help/repository/autolink-references-tab.png)
-4. 单击 **Add autolink reference（添加自动链接引用）**。 ![填写自动链接引用信息的按钮](/assets/images/help/repository/add-autolink-reference-details.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
+{% else %}
+1. 在左侧边栏中，单击 **Autolink references（自动链接引用）**。 ![左侧边栏中的自动链接引用选项卡](/assets/images/help/repository/autolink-references-tab.png)
+{% endif %}
+1. 单击 **Add autolink reference（添加自动链接引用）**。 ![填写自动链接引用信息的按钮](/assets/images/help/repository/add-autolink-reference-details.png)
 5. 在“Reference prefix（引用前缀）”下，输入您希望协作者用来为外部资源生成自动链接的、简短有意义的前缀。 ![输入外部系统缩写的字段](/assets/images/help/repository/add-reference-prefix-field.png)
 6. 在“Target URL（目标 URL）”中，输入您想要链接到的外部系统的链接。 确保将 `<num>` 保留为引用号的变量。 ![要输入外部系统 URL 的字段](/assets/images/help/repository/add-target-url-field.png)
 7. 单击 **Add autolink reference（添加自动链接引用）**。 ![添加自动链接引用的按钮](/assets/images/help/repository/add-autolink-reference.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
index 74af0c0bc4..ea7e21bb8a 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
@@ -28,7 +28,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. 在“Manage access（管理访问权限）”下的搜索字段中，开始输入您要查找的团队或人员的名称。 ![用于过滤具有访问权限的团队或人员列表的搜索字段](/assets/images/help/repository/manage-access-filter.png)
 
 ## 更改团队或人员的权限
@@ -42,7 +42,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. 在搜索字段中，开始输入要邀请的团队或人员的名称，然后单击匹配列表中的名称。 ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png)
 6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**. ![为团队或人员选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
@@ -51,7 +51,7 @@ For more information about repository roles, see "[Permission levels for a user
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-manage-access %}
+{% data reusables.repositories.click-collaborators-teams %}
 4. 在“Manage access（管理访问权限）”下，找到要删除其访问权限的团队或人员，然后单击 {% octicon "trash" aria-label="The trash icon" %}。 ![用于删除访问权限的回收站图标](/assets/images/help/repository/manage-access-remove.png)
 
 ## 延伸阅读
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/index.md b/translations/zh-CN/content/repositories/working-with-files/using-files/index.md
index e206e20283..8fd80fa5d2 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/index.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/index.md
@@ -8,7 +8,7 @@ versions:
   ghec: '*'
 children:
   - /navigating-code-on-github
-  - /tracking-changes-in-a-file
+  - /viewing-a-file
   - /getting-permanent-links-to-files
   - /working-with-non-code-files
 ---
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md
new file mode 100644
index 0000000000..7e9ec9f5dd
--- /dev/null
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -0,0 +1,49 @@
+---
+title: Viewing a file
+intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+redirect_from:
+  - /articles/using-git-blame-to-trace-changes-in-a-file
+  - /articles/tracing-changes-in-a-file
+  - /articles/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file
+  - /repositories/working-with-files/using-files/tracking-changes-in-a-file
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View files and track file changes
+---
+
+## Viewing or copying the raw file content
+
+With the raw view, you can view or copy the raw content of a file without any styling.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Click the file that you want to view.
+2. In the upper-right corner of the file view, click **Raw**. ![Screenshot of the Raw button in the file header](/assets/images/help/repository/raw-file-button.png)
+3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+
+## Viewing the line-by-line revision history for a file
+
+使用追溯视图时，您可以查看整个文件的逐行修订历史记录，也可以通过单击 {% octicon "versions" aria-label="The prior blame icon" %} 查看文件中某一行的修订历史记录。 每次单击 {% octicon "versions" aria-label="The prior blame icon" %} 后，您将看到该行以前的修订信息，包括提交更改的人员和时间。
+
+![Git 追溯视图](/assets/images/help/repository/git_blame.png)
+
+在文件或拉取请求中，您还可以使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} 菜单查看所选行或行范围的 Git 追溯。
+
+![带有查看所选行 Git 追溯选项的 Kebab 菜单](/assets/images/help/repository/view-git-blame-specific-line.png)
+
+{% tip %}
+
+**提示：**在命令行中，您还可以使用 `git blame` 查看文件内各行的修订历史记录。 更多信息请参阅 [Git 的 `git blame` 文档](https://git-scm.com/docs/git-blame)。
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. 单击以打开您想要查看其行历史记录的文件。
+3. 在文件视图的右上角，单击 **Blame（追溯）**可打开追溯视图。 ![追溯按钮](/assets/images/help/repository/blame-button.png)
+4. 要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到您有兴趣查看的更改。 ![追溯前按钮](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index afe2c5f187..e4dfcbc1ed 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -116,7 +116,7 @@ SVG 目前不支持内联脚本或动画。
 <script src="https://embed.github.com/view/3d/<username>/<repo>/<ref>/<path_to_file>"></script>
 ```
 
-例如，如果您的型号的 URL 是 [github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl)，则嵌入的代码是：
+For example, if your model's URL is [`github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl`](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl), your embed code would be:
 
 ```html
 <script src="https://embed.github.com/view/3d/skalnik/secret-bear-clip/master/stl/clip.stl"></script>
diff --git a/translations/zh-CN/content/rest/guides/building-a-ci-server.md b/translations/zh-CN/content/rest/guides/building-a-ci-server.md
index 25f48872e9..2b4594fa97 100644
--- a/translations/zh-CN/content/rest/guides/building-a-ci-server.md
+++ b/translations/zh-CN/content/rest/guides/building-a-ci-server.md
@@ -132,7 +132,7 @@ end
 
 所有这些通信都会流回我们的聊天室。 使用此示例并不需要构建自己的 CI 设置。 您始终可以依赖 [GitHub 集成][integrations]。
 
-[status API]: /rest/reference/repos#statuses
+[status API]: /rest/reference/commits#commit-statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
diff --git a/translations/zh-CN/content/rest/guides/delivering-deployments.md b/translations/zh-CN/content/rest/guides/delivering-deployments.md
index b3cf0bdffe..67f057f501 100644
--- a/translations/zh-CN/content/rest/guides/delivering-deployments.md
+++ b/translations/zh-CN/content/rest/guides/delivering-deployments.md
@@ -20,7 +20,7 @@ topics:
 
 本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将：
 
-* 合并拉取请求
+* Merge a pull request.
 * 在 CI 完成后，我们将相应地设置拉取请求的状态。
 * 合并拉取请求后，我们将在服务器上运行部署。
 
diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
index 63df4bdb73..17a964632a 100644
--- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
@@ -390,7 +390,7 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 
 `304` 状态表示该资源自上次请求以来没有发生改变，该响应将不包含任何正文。 As a bonus, `304` responses don't count against your [rate limit][rate-limiting].
 
-耶！ 现在您了解 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的基础知识了！
+现在您了解 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的基础知识了！
 
 * 基本 & OAuth 身份验证
 * 获取和创建仓库及议题
diff --git a/translations/zh-CN/content/rest/guides/index.md b/translations/zh-CN/content/rest/guides/index.md
index 21b80f4aa6..9769999965 100644
--- a/translations/zh-CN/content/rest/guides/index.md
+++ b/translations/zh-CN/content/rest/guides/index.md
@@ -25,4 +25,4 @@ children:
   - /getting-started-with-the-checks-api
 ---
 
-文档的这一部分旨在让您使用实际 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 应用程序开始运行。 我们将涵盖您需要知道的一切，从身份验证到操作结果，再到将结果与其他应用程序相结合。 这里的每个教程都包含一个项目，并且每个项目都将存储在我们的公共[平台样本](https://github.com/github/platform-samples)仓库中并形成文档。 ![Electrocat](/assets/images/electrocat.png)
+文档的这一部分旨在让您使用实际 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 应用程序开始运行。 我们将涵盖您需要知道的一切，从身份验证到操作结果，再到将结果与其他应用程序相结合。 这里的每个教程都包含一个项目，并且每个项目都将存储在我们的公共[平台样本](https://github.com/github/platform-samples)仓库中并形成文档。 ![The Octocat](/assets/images/electrocat.png)
diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
index a909156e4c..889a487617 100644
--- a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md
@@ -43,9 +43,9 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > Content-Type: application/json; charset=utf-8
 > ETag: "a00049ba79152d03380c34652f2cb612"
 > X-GitHub-Media-Type: github.v3
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4987
-> X-RateLimit-Reset: 1350085394{% ifversion ghes %}
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4987
+> x-ratelimit-reset: 1350085394{% ifversion ghes %}
 > X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %}
 > X-GitHub-Enterprise-Version: GitHub AE{% endif %}
 > Content-Length: 5
@@ -411,16 +411,16 @@ The returned HTTP headers of any API request show your current rate limit status
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 56
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 56
+> x-ratelimit-reset: 1372700873
 ```
 
 Header Name | Description
 -----------|-----------|
-`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour.
-`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window.
-`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
+`x-ratelimit-limit` | The maximum number of requests you're permitted to make per hour.
+`x-ratelimit-remaining` | The number of requests remaining in the current rate limit window.
+`x-ratelimit-reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
 
 If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
 
@@ -434,9 +434,9 @@ If you exceed the rate limit, an error response returns:
 ```shell
 > HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
-> X-RateLimit-Limit: 60
-> X-RateLimit-Remaining: 0
-> X-RateLimit-Reset: 1377013266
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 0
+> x-ratelimit-reset: 1377013266
 
 > {
 >    "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
@@ -452,9 +452,9 @@ If your OAuth App needs to make unauthenticated calls with a higher rate limit,
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
 > HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4966
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4966
+> x-ratelimit-reset: 1372700873
 ```
 
 {% note %}
@@ -541,9 +541,9 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
 > HTTP/2 304
@@ -551,18 +551,18 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
 > HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
-> X-RateLimit-Limit: 5000
-> X-RateLimit-Remaining: 4996
-> X-RateLimit-Reset: 1372700873
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
 ```
 
 ## Cross origin resource sharing
@@ -580,7 +580,7 @@ Here's a sample request sent from a browser hitting
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
 HTTP/2 302
 Access-Control-Allow-Origin: *
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
 
 This is what the CORS preflight request looks like:
@@ -591,7 +591,7 @@ HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
-Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 Access-Control-Max-Age: 86400
 ```
 
@@ -609,9 +609,9 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > /**/foo({
 >   "meta": {
 >     "status": 200,
->     "X-RateLimit-Limit": "5000",
->     "X-RateLimit-Remaining": "4966",
->     "X-RateLimit-Reset": "1372700873",
+>     "x-ratelimit-limit": "5000",
+>     "x-ratelimit-remaining": "4966",
+>     "x-ratelimit-reset": "1372700873",
 >     "Link": [ // pagination headers and other links
 >       ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}]
 >     ]
@@ -712,3 +712,4 @@ If no `Time-Zone` header is specified and you make an authenticated call to the
 If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
 
 [pagination-guide]: /guides/traversing-with-pagination
+
diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
index c046cc50c1..52f78a4d1a 100644
--- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
@@ -175,6 +175,9 @@ _搜索_
 {% ifversion fpt -%}
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif -%}
+{% ifversion ghes > 3.3 -%}
+- [`GET /repos/:owner/:repo/replicas/caches`](/rest/reference/repos#list-repository-cache-replication-status) (:read)
+{% endif -%}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% ifversion fpt -%}
diff --git a/translations/zh-CN/content/rest/reference/pulls.md b/translations/zh-CN/content/rest/reference/pulls.md
index f368bb0351..4a5e75bf21 100644
--- a/translations/zh-CN/content/rest/reference/pulls.md
+++ b/translations/zh-CN/content/rest/reference/pulls.md
@@ -45,7 +45,7 @@ miniTocMaxHeadingLevel: 3
 | `review_comments` | 此拉取请求的[审查评论](/rest/reference/pulls#comments)的 API 位置。                                    |
 | `review_comment`  | 用于为此拉取请求仓库中的[审查评论](/rest/reference/pulls#comments)构建 API 位置的 [URL 模板](/rest#hypermedia)。 |
 | `commits`         | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。                                     |
-| `状态`              | 此拉取请求的[提交状态](/rest/reference/repos#statuses)的 API 位置，即其`头部`分支的状态。                        |
+| `状态`              | 此拉取请求的[提交状态](/rest/reference/commits#commit-statuses)的 API 位置，即其`头部`分支的状态。               |
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/zh-CN/content/rest/reference/scim.md b/translations/zh-CN/content/rest/reference/scim.md
index ca9c457f0c..8a884ec24d 100644
--- a/translations/zh-CN/content/rest/reference/scim.md
+++ b/translations/zh-CN/content/rest/reference/scim.md
@@ -33,15 +33,15 @@ SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data v
 
 ### 支持的 SCIM 用户属性
 
-| 名称               | 类型    | 描述                                                                                                                                                                                    |
-| ---------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `userName`       | `字符串` | 用户的用户名。                                                                                                                                                                               |
-| `name.givenName` | `字符串` | 用户的名字                                                                                                                                                                                 |
-| `name.lastName`  | `字符串` | 用户的姓氏。                                                                                                                                                                                |
-| `emails`         | `数组`  | 用户电子邮件列表。                                                                                                                                                                             |
-| `externalId`     | `字符串` | 此标识符由 SAML 提供程序生成，并且被 SAML 提供程序用作唯一 ID 来匹配 GitHub 用户。 您可以在 SAML 提供程序上查找用户的 `externalID`，或者使用 [List SCIM 预配的身份](#list-scim-provisioned-identities)端点并过滤其他已知的属性，如用户的 GitHub 用户名或电子邮件地址。 |
-| `id`             | `字符串` | GitHub SCIM 端点生成的标识符。                                                                                                                                                                 |
-| `active`         | `布尔值` | 用于表示身份是处于活动状态 (true) 还是应解除预配 (false)。                                                                                                                                                 |
+| 名称                | 类型    | 描述                                                                                                                                                                                    |
+| ----------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName`        | `字符串` | 用户的用户名。                                                                                                                                                                               |
+| `name.givenName`  | `字符串` | 用户的名字                                                                                                                                                                                 |
+| `name.familyName` | `字符串` | 用户的姓氏。                                                                                                                                                                                |
+| `emails`          | `数组`  | 用户电子邮件列表。                                                                                                                                                                             |
+| `externalId`      | `字符串` | 此标识符由 SAML 提供程序生成，并且被 SAML 提供程序用作唯一 ID 来匹配 GitHub 用户。 您可以在 SAML 提供程序上查找用户的 `externalID`，或者使用 [List SCIM 预配的身份](#list-scim-provisioned-identities)端点并过滤其他已知的属性，如用户的 GitHub 用户名或电子邮件地址。 |
+| `id`              | `字符串` | GitHub SCIM 端点生成的标识符。                                                                                                                                                                 |
+| `active`          | `布尔值` | 用于表示身份是处于活动状态 (true) 还是应解除预配 (false)。                                                                                                                                                 |
 
 {% note %}
 
diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
index f7178fa0d2..19cb5fd638 100644
--- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
+++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
@@ -47,19 +47,19 @@ topics:
 
 `sort:author-date` 限定符按作者日期降序或升序排序。
 
-| 限定符                                          | 示例                                                                                                                                                                                                                                  |
-| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `sort:author-date` 或 `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按作者日期降序排序。         |
-| `sort:author-date-asc`                       | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按作者日期升序排序。 |
+| 限定符                                          | 示例                                                                                                                                                                                                                                                                                                      |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:author-date` 或 `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按作者日期降序排序。                                                                             |
+| `sort:author-date-asc`                       | [**`feature org:github sort:author-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending author date. |
 
 ## 按提交者日期排序
 
 `sort:committer-date` 限定符按提交者日期降序或升序排序。
 
-| 限定符                                                | 示例                                                                                                                                                                                                                                         |
-| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `sort:committer-date` 或 `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按提交者日期降序排序。         |
-| `sort:committer-date-asc`                          | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按提交者日期升序排序。 |
+| 限定符                                                | 示例                                                                                                                                                                                                                                                                                                               |
+| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:committer-date` 或 `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按提交者日期降序排序。                                                                               |
+| `sort:committer-date-asc`                          | [**`feature org:github sort:committer-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending committer date. |
 
 ## 按更新日期排序
 
@@ -72,5 +72,5 @@ topics:
 
 ## 延伸阅读
 
-- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)"
+- “[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”
 - "[过滤和搜索议题和拉取请求](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"
diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index a2e62f3188..c4095de808 100644
--- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -73,9 +73,10 @@ shortTitle: 了解搜索语法
 
 缩小搜索结果范围的另一种途径是排除特定的子集。 您可以为任何搜索限定符添加 `-` 前缀，以排除该限定符匹配的所有结果。
 
-| 查询                         | 示例                                                                                                                                                             |
-| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>-<em>QUALIFIER</em></code> | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** 匹配提及 @defunkt 且不在 GitHub 组织仓库中的议题. |
+| 查询                         | 示例                                                                                                                                                                                                                                              |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>QUALIFIER</em></code> | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript. |
+|                            | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization                        |
 
 ## 对带有空格的查询使用引号
 
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-code.md b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
index 50d2118af9..0c70513149 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
@@ -62,11 +62,11 @@ topics:
 
 您可使用 `path` 限定符搜索仓库中特定位置显示的源代码。 使用 `path:/` 可搜索位于仓库根目录级别的文件。 或者，指定目录名称或目录路径以搜索位于该命令或其任何子目录中的文件。
 
-| 限定符                        | 示例                                                                                                                                                                                                                                                                                                                               |
-| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>path:/</code>  | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) 匹配位于仓库根目录级别且含有 "octocat" 字样的 _readme_ 文件。                                                                                                                                                        |
-| <code>path:<em>DIRECTORY</em></code>  | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the <em>cgi-bin</em> directory, or in any of its subdirectories.                                                                                              |
-| <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
+| 限定符                        | 示例                                                                                                                                                                                                                                                                                                                                 |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>path:/</code>  | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) 匹配位于仓库根目录级别且含有 "octocat" 字样的 _readme_ 文件。                                                                                                                                                          |
+| <code>path:<em>DIRECTORY</em></code>  | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the <em>cgi-bin</em> directory, or in any of its subdirectories.                                                                                                |
+| <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
 
 ## 按语言搜索
 <!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md
index bb4e85932f..afd255ec34 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md
@@ -31,10 +31,10 @@ redirect_from:
 
 要查找特定用户或组织拥有的包，请使用 `user` 或 `org` 限定符。
 
-| 限定符                       | 示例                                                                                                                                      |
-| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>user:<em>USERNAME</em></code> | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) 匹配 @codertocat 拥有的包                          |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) 匹配 {% data variables.product.prodname_dotcom %} 组织拥有的包 |
+| 限定符                       | 示例                                                                                                                                                                         |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat                                         |
+| <code>org:<em>ORGNAME</em></code> | [**`org:github`**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization |
 
 ## 按包可见性过滤
 
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
index 4cf28ebd0c..974fac0002 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
@@ -111,17 +111,17 @@ shortTitle: 搜索仓库
 
 您可以根据仓库中代码的语言搜索仓库。
 
-| 限定符                       | 示例                                                                                                                                             |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) 匹配具有 "rails" 字样、以 JavaScript 编写的仓库。 |
+| 限定符                       | 示例                                                                                                                                                                                      |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. |
 
 ## 按主题搜索
 
 您可以找到按特定主题分类的所有仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。
 
-| 限定符                       | 示例                                                                                                                                      |
-| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults)匹配已归类为 "jekyll" 主题的仓库。 |
+| 限定符                       | 示例                                                                                                                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll." |
 
 ## 按主题数量搜索
 
@@ -178,10 +178,10 @@ shortTitle: 搜索仓库
 
 您可以使用限定符 `help-wanted-issues:>n` 和 `good-first-issues:>n` 搜索具有最少数量标签为 `help-wanted` 或 `good-first-issue` 议题的仓库。 更多信息请参阅“[通过标签鼓励对项目做出有益的贡献](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)”。
 
-| 限定符                        | 示例                                                                                                                                                                                             |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) 匹配具有超过两个标签为 `good-first-issue` 的议题且包含 "javascript" 字样的仓库。 |
-| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) 匹配具有超过四个标签为 `help-wanted` 的议题且包含 "React" 字样的仓库。                   |
+| 限定符                        | 示例                                                                                                                                                                                                                                                     |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `good-first-issues:>n`  | [**`good-first-issues:&gt;2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) 匹配具有超过四个标签为 `help-wanted` 的议题且包含 "React" 字样的仓库。                                                                           |
 
 ## 基于赞助能力的搜索
 
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 1e808b5920..e0f96871ba 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -103,18 +103,18 @@ shortTitle: 搜索议题和 PR
 
 `mentions` 限定符查找提及特定用户的议题。 更多信息请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”。
 
-| 限定符                       | 示例                                                                                                                                 |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) 匹配含有 "resque" 字样、提及 @defunkt 的议题。 |
+| 限定符                       | 示例                                                                                                                                                              |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>mentions:<em>USERNAME</em></code> | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. |
 
 ## 按团队提及搜索
 
 对于您所属的组织和团队，您可以使用 `team` 限定符查找提及该组织内特定团队的议题或拉取请求。 将这些示例名称替换为您的组织和团队的名称以执行搜索。
 
-| 限定符                       | 示例                                                            |
-| ------------------------- | ------------------------------------------------------------- |
-| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** 匹配提及 `@jekyll/owners` 团队的议题。           |
-|                           | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。 |
+| 限定符                       | 示例                                                                                    |
+| ------------------------- | ------------------------------------------------------------------------------------- |
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **`team:jekyll/owners`** matches issues where the `@jekyll/owners` team is mentioned. |
+|                           | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。                         |
 
 ## 按评论者搜索
 
@@ -176,7 +176,7 @@ shortTitle: 搜索议题和 PR
 
 ## 按提交状态搜索
 
-您可以基于提交的状态过滤拉取请求。 This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service.
+您可以基于提交的状态过滤拉取请求。 This is especially useful if you are using [the Status API](/rest/reference/commits#commit-statuses) or a CI service.
 
 | 限定符              | 示例                                                                                                                                                                                          |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -291,19 +291,19 @@ shortTitle: 搜索议题和 PR
 
 {% data reusables.search.date_gt_lt %}
 
-| 限定符                        | 示例                                                                                                                                                                                                          |
-| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) 匹配 2011 年以前合并的 JavaScript 仓库中的拉取请求。                                     |
-|                            | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) 匹配 2014 年 5 月之后合并、标题中含有 "fast" 字样、以 Ruby 编写的拉取请求。 |
+| 限定符                        | 示例                                                                                                                                                                                                                      |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>merged:<em>YYYY-MM-DD</em></code> | [**`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. |
+|                            | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) 匹配 2014 年 5 月之后合并、标题中含有 "fast" 字样、以 Ruby 编写的拉取请求。             |
 
 ## 基于拉取请求是否已合并搜索
 
 您可以使用 `is` 限定符基于拉取请求已合并还是未合并进行过滤。
 
-| 限定符           | 示例                                                                                                                                  |
-| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `is:merged`   | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) 匹配含有 "bugfix" 字样的已合并拉取请求。 |
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) 匹配含有 "error" 字样的已关闭议题和拉取请求。           |
+| 限定符           | 示例                                                                                                                                                       |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bug." |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) 匹配含有 "error" 字样的已关闭议题和拉取请求。                                |
 
 ## 基于仓库是否已存档搜索
 
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
index 6036891b2c..9c1ef47b56 100644
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -49,6 +49,43 @@ shortTitle: 管理付款等级
 {% data reusables.sponsors.tier-update %}
 {% data reusables.sponsors.retire-tier %}
 
+## Adding a repository to a sponsorship tier
+
+{% data reusables.sponsors.sponsors-only-repos %}
+
+### About adding repositories to a sponsorship tier
+
+To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository.
+
+When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled.
+
+Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier.
+
+You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync.
+
+### About transfers for repositories that are added to sponsorship tiers
+
+If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected.
+
+- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors.
+- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository.
+- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository.
+
+### Adding a repository a sponsorship tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+1. Select **Grant sponsors access to a private repository**.
+
+   ![Screenshot of checkbox to grant sponsors access to a private repository](/assets/images/help/sponsors/grant-sponsors-access-to-repo-checkbox.png)
+
+1. Select the dropdown menu and click the repository you want to add.
+
+   ![Screenshot of dropdown menu to choose the repository to grant sponsors access to](/assets/images/help/sponsors/grant-sponsors-access-to-repo-dropdown.png)
+
+{% data reusables.sponsors.tier-update %}
+
 ## 启用具有自定义金额的等级
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
diff --git a/translations/zh-CN/data/features/code-scanning-task-lists.yml b/translations/zh-CN/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..0de30490f7
--- /dev/null
+++ b/translations/zh-CN/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/translations/zh-CN/data/features/codeql-ml-queries.yml b/translations/zh-CN/data/features/codeql-ml-queries.yml
new file mode 100644
index 0000000000..c74f86b77f
--- /dev/null
+++ b/translations/zh-CN/data/features/codeql-ml-queries.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5604.
+#Documentation for the beta release of CodeQL queries boosted by machine learning
+#to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/zh-CN/data/features/github-actions-in-dependency-graph.yml b/translations/zh-CN/data/features/github-actions-in-dependency-graph.yml
new file mode 100644
index 0000000000..1690a6b771
--- /dev/null
+++ b/translations/zh-CN/data/features/github-actions-in-dependency-graph.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5813.
+#Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
+versions:
+  fpt: '*'
+  ghae: 'issue-5813'
+  ghec: '*'
diff --git a/translations/zh-CN/data/features/security-overview-views.yml b/translations/zh-CN/data/features/security-overview-views.yml
new file mode 100644
index 0000000000..bef4f54c9d
--- /dev/null
+++ b/translations/zh-CN/data/features/security-overview-views.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5503.
+#Documentation for the security overview individual views
+versions:
+  ghes: '> 3.4'
+  ghae: 'issue-5503'
+  ghec: '*'
diff --git a/translations/zh-CN/data/learning-tracks/actions.yml b/translations/zh-CN/data/learning-tracks/actions.yml
index 2c53f7896e..79cafb12fa 100644
--- a/translations/zh-CN/data/learning-tracks/actions.yml
+++ b/translations/zh-CN/data/learning-tracks/actions.yml
@@ -41,6 +41,7 @@ adopting_github_actions_for_your_enterprise:
   title: 'Adopt GitHub Actions for your enterprise'
   description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
   guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
     - /actions/learn-github-actions/understanding-github-actions
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
diff --git a/translations/zh-CN/data/learning-tracks/admin.yml b/translations/zh-CN/data/learning-tracks/admin.yml
index b918b1009b..6cceba3ea6 100644
--- a/translations/zh-CN/data/learning-tracks/admin.yml
+++ b/translations/zh-CN/data/learning-tracks/admin.yml
@@ -42,6 +42,7 @@ adopting_github_actions_for_your_enterprise:
   title: 'Adopt GitHub Actions for your enterprise'
   description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.'
   guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
     - /actions/learn-github-actions/understanding-github-actions
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
diff --git a/translations/zh-CN/data/product-examples/README.md b/translations/zh-CN/data/product-examples/README.md
index eab550485d..f21daf87a5 100644
--- a/translations/zh-CN/data/product-examples/README.md
+++ b/translations/zh-CN/data/product-examples/README.md
@@ -2,7 +2,7 @@
 
 使用 `product-landing` 布局的页面可以选择包含 `Examples` 部分。 目前，我们支持三种类型的示例：
 
-1. 代码示例 请参阅 https://docs.github.com/en/actions#code-examples。
+1. 代码示例 请参阅 https://docs.github.com/en/codespaces#code-examples。
 
 2. 社区示例 请参阅 https://docs.github.com/en/discussions#community-examples。
 
@@ -10,7 +10,7 @@
 
 ## 工作原理
 
-每个产品的示例数据定义在 `data/product-landing-examples` 中，名为 **product** 的子目录中，以及名为 **example type** 的 YML 文件中（例如，`data/product-examples/sponsors/user-examples.yml` 或 `data/product-examples/actions/code-examples.yml`）。 我们目前只支持每个产品一种示例。
+Example data for each product is defined in `data/product-landing-examples`, in a subdirectory named for the **product** and a YML file named for the **example type** (e.g., `data/product-examples/sponsors/user-examples.yml` or `data/product-examples/codespaces/code-examples.yml`). 我们目前只支持每个产品一种示例。
 
 ### 版本
 
diff --git a/translations/zh-CN/data/product-examples/actions/code-examples.yml b/translations/zh-CN/data/product-examples/actions/code-examples.yml
deleted file mode 100644
index 92d52cb5bf..0000000000
--- a/translations/zh-CN/data/product-examples/actions/code-examples.yml
+++ /dev/null
@@ -1,335 +0,0 @@
----
-- 
-  title: 示例服务
-  description: 使用服务容器的示例工作流程
-  languages: JavaScript
-  href: actions/example-services
-  tags:
-    - 服务容器
-- 
-  title: 声明设置 GitHub 标签
-  description: 声明设置跨仓库标签的 GitHub Actions
-  languages: JavaScript
-  href: lannonbr/issue-label-manager-action
-  tags:
-    - 议题
-    - labels
-- 
-  title: 声明同步 GitHub 标签
-  description: 以声明方式同步 GitHub 标签的 GitHub Actions
-  languages: 'Go, Dockerfile'
-  href: micnncim/action-label-syncer
-  tags:
-    - 议题
-    - labels
-- 
-  title: 向 GitHub 添加版本
-  description: 在操作中发布 GitHub 版本
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Github-Release-Action
-  tags:
-    - 发行版
-    - 发布
-- 
-  title: 向 Dockerhub 发布 Docker 映像
-  description: 用于生成和发布 Docker 映像的 GitHub 操作
-  languages: 'Dockerfile, Shell'
-  href: elgohr/Publish-Docker-Github-Action
-  tags:
-    - docker
-    - 发布
-    - 构建
-- 
-  title: 使用文件中的内容创建议题
-  description: 使用文件中的内容创建议题的 GitHub Actions
-  languages: 'JavaScript, Python'
-  href: peter-evans/create-issue-from-file
-  tags:
-    - 议题
-- 
-  title: 使用资产发布 GitHub 版本
-  description: 用于创建 GitHub 版本的 GitHub Actions
-  languages: 'TypeScript, Shell, JavaScript'
-  href: softprops/action-gh-release
-  tags:
-    - 发行版
-    - 发布
-- 
-  title: GitHub Project Automation+
-  description: 使用任何 web 挂钩事件自动执行 GitHub 项目卡
-  languages: JavaScript
-  href: alex-page/github-project-automation-plus
-  tags:
-    - projects
-    - automation
-    - 议题
-    - 拉取请求
-- 
-  title: 使用 Web 界面在本地运行 GitHub Actions
-  description: 本地运行 GitHub Actions 工作流程（本地）
-  languages: 'JavaScript, HTML, Dockerfile, CSS'
-  href: phishy/wflow
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: 在本地运行 GitHub Actions
-  description: 在终端中本地运行 GitHub Actions
-  languages: 'Go, Shell'
-  href: nektos/act
-  tags:
-    - local-development
-    - devops
-    - docker
-- 
-  title: 生成和发布 Android 调试 APK
-  description: 从 Android 项目生成和发布调试 APK
-  languages: 'Shell, Dockerfile'
-  href: ShaunLWM/action-release-debugapk
-  tags:
-    - android
-    - 构建
-- 
-  title: 为 GitHub Actions 生成序列生成编号
-  description: 用于生成序列生成编号的 GitHub Actions。
-  languages: JavaScript
-  href: einaregilsson/build-number
-  tags:
-    - 构建
-    - automation
-- 
-  title: 要推回到仓库的 GitHub Actions
-  description: 将 Git 更改推送到 GitHub 仓库，而不会遇到身份验证困难
-  languages: 'JavaScript, Shell'
-  href: ad-m/github-push-action
-  tags:
-    - 发布
-- 
-  title: 根据您的事件生成发行说明
-  description: 根据事件自动生成发行说明的操作
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/release-notes-generator-action
-  tags:
-    - 发行版
-    - 发布
-- 
-  title: 基于提供的 markdown 文件创建 GitHub wiki 页面
-  description: 基于提供的 markdown 文件创建 GitHub wiki 页面
-  languages: 'Shell, Dockerfile'
-  href: Decathlon/wiki-page-creator-action
-  tags:
-    - wiki
-    - 发布
-- 
-  title: 自动标记您的拉取请求（使用提交的文件）
-  description: 自动标记拉取请求（使用提交的文件）的 GitHub 操作
-  languages: 'TypeScript, Dockerfile, JavaScript'
-  href: Decathlon/pull-request-labeler-action
-  tags:
-    - projects
-    - 议题
-    - labels
-- 
-  title: 根据作者团队名称向拉取请求添加标签
-  description: 根据作者名称标记拉取请求的 GitHub 操作
-  languages: 'TypeScript, JavaScript'
-  href: JulienKode/team-labeler-action
-  tags:
-    - 拉取请求
-    - labels
-- 
-  title: 使用 PR/Push 获取文件更改列表
-  description: 此操作可让您获取仓库已更改的文件的输出
-  languages: 'TypeScript, Shell, JavaScript'
-  href: trilom/file-changes-action
-  tags:
-    - 工作流程
-    - 仓库
-- 
-  title: 任何工作流程中的私人操作
-  description: 允许轻松重复利用私人 GitHub Actions
-  languages: 'TypeScript, JavaScript, Shell'
-  href: InVisionApp/private-action-loader
-  tags:
-    - 工作流程
-    - tools
-- 
-  title: 使用议题的内容标记您的议题
-  description: 使用标签和受理人自动标记议题的 GitHub Actions
-  languages: 'JavaScript, TypeScript'
-  href: damccorm/tag-ur-it
-  tags:
-    - 工作流程
-    - tools
-    - labels
-    - 议题
-- 
-  title: 回滚 GitHub 版本
-  description: 回滚或删除版本的 GitHub Actions
-  languages: 'JavaScript'
-  href: author/action-rollback
-  tags:
-    - 工作流程
-    - 发行版
-- 
-  title: 锁定已关闭的议题和拉取请求
-  description: 在一段时间不活动后锁定关闭的议题和拉取请求的 GitHub Actions
-  languages: 'JavaScript'
-  href: dessant/lock-threads
-  tags:
-    - 议题
-    - 拉取请求
-    - 工作流程
-- 
-  title: 获取两个分支之间的提交差异数
-  description: 此 GitHub Actions 比较两个分支，并提供它们之间的提交数
-  languages: 'JavaScript, Shell'
-  href: jessicalostinspace/commit-difference-action
-  tags:
-    - 提交
-    - 差异
-    - 工作流程
-- 
-  title: 基于 Git 引用生成发行说明
-  description: 生成变更日志和发行说明的 GitHub Actions
-  languages: 'JavaScript, Shell'
-  href: metcalfc/changelog-generator
-  tags:
-    - cicd
-    - release-notes
-    - 工作流程
-    - 变更日志
-- 
-  title: 对 GitHub 仓库和提交实施策略
-  description: 管道的策略实施
-  languages: 'Go, Makefile, Dockerfile, Shell'
-  href: talos-systems/conform
-  tags:
-    - docker
-    - build-automation
-    - 工作流程
-- 
-  title: 基于议题自动标记
-  description: 根据议题描述自动标记议题
-  languages: 'TypeScript, JavaScript, Dockerfile'
-  href: Renato66/auto-label
-  tags:
-    - labels
-    - 工作流程
-    - automation
-- 
-  title: 将配置的 GitHub Actions 更新到最新版本
-  description: 用于检查所有操作是否为最新的 CLI 工具
-  languages: 'C#, Inno Setup, PowerShell, Shell'
-  href: fabasoad/ghacu
-  tags:
-    - versions
-    - cli
-    - 工作流程
-- 
-  title: 创建议题分支
-  description: 自动创建议题分支的 GitHub Actions
-  languages: 'JavaScript, Shell'
-  href: robvanderleek/create-issue-branch
-  tags:
-    - probot
-    - 议题
-    - labels
-- 
-  title: 删除旧构件
-  description: 自定义构件清理
-  languages: 'JavaScript, Shell'
-  href: c-hive/gha-remove-artifacts
-  tags:
-    - 构件
-    - 工作流程
-- 
-  title: 将定义的文件/二进制文件同步到 Wiki 或外部仓库
-  description: 自动将更改同步到外部仓库（例如 wiki）的 GitHub Actions
-  languages: 'Shell, Dockerfile'
-  href: kai-tub/external-repo-sync-action
-  tags:
-    - wiki
-    - sync
-    - 工作流程
-- 
-  title: 基于任何文件创建/更新/删除 GitHub Wiki 页面
-  description: 使用 rsync 更新 GitHub wiki，允许排除文件和目录以及实际删除文件
-  languages: 'Shell, Dockerfile'
-  href: Andrew-Chen-Wang/github-wiki-action
-  tags:
-    - wiki
-    - docker
-    - 工作流程
-- 
-  title: Prow GitHub Actions
-  description: 策略实施、聊天操作和自动 PR 合并的自动化
-  languages: 'TypeScript, JavaScript'
-  href: jpmcb/prow-github-actions
-  tags:
-    - chat-ops
-    - prow
-    - 工作流程
-- 
-  title: 检查工作流程中的 GitHub 状态
-  description: 检查工作流程中的 GitHub 状态
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-status
-  tags:
-    - 状态
-    - 监视
-    - 工作流程
-- 
-  title: 将 GitHub 上的标签作为代码管理
-  description: 用于管理标签的 GitHub Actions（创建/重命名/更新/删除）
-  languages: 'TypeScript, JavaScript'
-  href: crazy-max/ghaction-github-labeler
-  tags:
-    - labels
-    - 工作流程
-    - automation
-- 
-  title: 在免费和开源项目中分配资金
-  description: 持续向项目贡献者和依赖项分配资金
-  languages: 'Python, Dockerfile, Shell, Ruby'
-  href: protontypes/libreselery
-  tags:
-    - sponsors
-    - funding
-    - payment
-- 
-  title: GitHub 的 Herald 规则
-  description: 将审查者、订阅者、标签和受理人添加到您的 PR
-  languages: 'TypeScript, JavaScript'
-  href: gagoar/use-herald-action
-  tags:
-    - reviewers
-    - labels
-    - assignees
-    - 拉取请求
-- 
-  title: 代码所有者验证器
-  description: 确保 GitHub CODEOWNERS 文件的正确性，支持公共和私有 GitHub 仓库以及 GitHub Enterprise 安装
-  languages: 'Go, Shell, Makefile, Dockerfile'
-  href: mszostok/codeowners-validator
-  tags:
-    - codeowners
-    - 验证
-    - 工作流程
-- 
-  title: Copybara 操作
-  description: 在仓库之间移动和转化代码（非常适合从单个仓库维护几个仓库）
-  languages: 'TypeScript, JavaScript, Shell'
-  href: olivr/copybara-action
-  tags:
-    - monorepo
-    - copybara
-    - 工作流程
-- 
-  title: 将静态文件部署到 GitHub Pages
-  description: 用于将网站自动发布到 GitHub Pages 的 GitHub Actions
-  languages: 'TypeScript, JavaScript'
-  href: peaceiris/actions-gh-pages
-  tags:
-    - 发布
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml
index b66f9f8886..c97c31e4b6 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml
@@ -2,8 +2,8 @@
 date: '2020-08-11'
 sections:
   security_fixes:
-    - '**关键：**在 GitHub 页面中发现了一个远程代码执行漏洞，允许攻击者执行命令，作为构建 GitHub Pages 网站的一部分。此问题源于在 Pages 构建过程中使用了过时和有漏洞的依赖项。要利用此漏洞，攻击者需要在 GitHub Enterprise Server 实例 上构建 GitHub Pages 站点的权限。此漏洞影响 GitHub Enterprise Server 的所有版本。为缓解此漏洞的影响，Kramdown 已更新以解决 CVE-2020-14001。{% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
-    - '**高：**攻击者在 GitHub Enterprise Server 上执行时可能会将恶意参数注入 Git 子命令。这可能允许攻击者用部分用户控制的内容覆盖任意文件，并可能在 GitHub Enterprise Server 实例上执行任意命令。要利用此漏洞，攻击者需要访问 GitHub Enterprise Server 实例中仓库的权限。但由于已实施其他保护措施，因此我们无法确定积极利用这一漏洞的方法。此漏洞是通过 GitHub Security Bug Bounty 计划报告的。 {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance.  This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
+    - '**High:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
     - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
   bugs:
     - 'Consul 配置错误阻止在独立实例中处理一些后台任务。 {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml
index b5622c9f32..01f9c1eed7 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml
@@ -2,7 +2,7 @@ date: '2020-08-26'
 sections:
   security_fixes:
     - >-
-      **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
+      {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
       https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}
     - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}'
     - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml
index 49b79ff5ee..bf65a175da 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml
@@ -2,8 +2,8 @@
 date: '2020-08-11'
 sections:
   security_fixes:
-    - '**关键：**在 GitHub 页面中发现了一个远程代码执行漏洞，允许攻击者执行命令，作为构建 GitHub Pages 网站的一部分。此问题源于在 Pages 构建过程中使用了过时和有漏洞的依赖项。要利用此漏洞，攻击者需要在 GitHub Enterprise Server 实例 上构建 GitHub Pages 站点的权限。此漏洞影响 GitHub Enterprise Server 的所有版本。为缓解此漏洞的影响，Kramdown 已更新以解决 CVE-2020-14001。 {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
-    - '**高：**攻击者在 GitHub Enterprise Server 上执行时可能会将恶意参数注入 Git 子命令。这可能允许攻击者用部分用户控制的内容覆盖任意文件，并可能在 GitHub Enterprise Server 实例上执行任意命令。要利用此漏洞，攻击者需要访问 GHES 实例中仓库的权限。但由于已实施其他保护措施，因此我们无法确定积极利用这一漏洞的方法。此漏洞是通过 GitHub Security Bug Bounty 计划报告的。 {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance.  This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}'
+    - '**High:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}'
     - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
   bugs:
     - 'Consul 配置错误阻止在独立实例中处理一些后台任务。 {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml
index f8d72193cd..c9ef772868 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml
@@ -2,9 +2,9 @@ date: '2020-08-26'
 sections:
   security_fixes:
     - >-
-      **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
+      {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700,
       https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %}
-    - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
+    - '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}'
     - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}'
   bugs:
     - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml
index 2c0ec91ff6..9ccd94c77a 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml
@@ -3,6 +3,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions.
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.
     - A misconfiguration in the Management Console caused scheduling errors.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml
index 3474566233..612a802d17 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml
new file mode 100644
index 0000000000..0145605022
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml
@@ -0,0 +1,21 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - 当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml
index 5b0a24dfa4..781daeca61 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml
@@ -3,6 +3,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions.
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.
     - A misconfiguration in the Management Console caused scheduling errors.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml
index 7976fb59e4..e2e2b72cd5 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml
new file mode 100644
index 0000000000..ae3114314a
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml
@@ -0,0 +1,25 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - Several documentation links resulted in a 404 Not Found error.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`.
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml
index 5569566ebe..f8311e8c59 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml
@@ -3,6 +3,7 @@ date: '2021-12-07'
 sections:
   security_fixes:
     - Support bundles could include sensitive files if they met a specific set of conditions.
+    - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598).
   bugs:
     - In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.`
     - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml
index 7cd48b20a1..4ea8259572 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml
new file mode 100644
index 0000000000..4ba202aa11
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml
@@ -0,0 +1,26 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
index 805090cf85..9fea6fe634 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
@@ -2,7 +2,7 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
     - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.'
   known_issues:
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml
new file mode 100644
index 0000000000..06aa240abb
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml
@@ -0,0 +1,29 @@
+---
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - '**MEDIUM**:  Secret Scanning API calls could return alerts for repositories outside the scope of the request.'
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted.
+    - Migrations could fail when {% data variables.product.prodname_actions %} was enabled.
+    - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC.
+    - Spurious error messages concerning the `cloud-config.service` would be output to the console.
+    - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`.
+    - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time.
+    - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group.
+    - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly.
+    - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated.
+    - A long-running database migration related to Security Alert settings could delay upgrade completion.
+  changes:
+    - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
diff --git a/translations/zh-CN/data/reusables/actions/oidc-permissions-token.md b/translations/zh-CN/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..abc7dba354
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,13 @@
+The job or workflow run requires a `permissions` setting with [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). This allows the JWT to be requested from GitHub's OIDC provider using one of these approaches:
+
+- Using environment variables on the runner (`ACTIONS_ID_TOKEN_REQUEST_URL` and `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Using `getIDToken()` from the Actions toolkit.
+
+If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
+
+```yaml{:copy}
+permissions:
+  id-token: write
+```
+
+You may need to specify additional permissions here, depending on your workflow's requirements. 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
index bcf62c40c4..8bf9c2d08d 100644
--- a/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
+++ b/translations/zh-CN/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -52,7 +52,7 @@ on:
       - '!sub-project/docs/**'
 ```
 
-### Git 差异比较
+#### Git 差异比较
 
 {% note %}
 
diff --git a/translations/zh-CN/data/reusables/apps/checks-availability.md b/translations/zh-CN/data/reusables/apps/checks-availability.md
index c0b3ffd3cd..afea5d2e35 100644
--- a/translations/zh-CN/data/reusables/apps/checks-availability.md
+++ b/translations/zh-CN/data/reusables/apps/checks-availability.md
@@ -1 +1 @@
-检查 API 的写入权限仅适用于 GitHub 应用程序。 OAuth 应用程序和经过身份验证的用户可以查看检查运行和检查套件，但无法创建它们。 如果您没有构建 GitHub 应用程序，您可能对[状态 API](/rest/reference/repos#statuses) 感兴趣。
+检查 API 的写入权限仅适用于 GitHub 应用程序。 OAuth 应用程序和经过身份验证的用户可以查看检查运行和检查套件，但无法创建它们。 如果您没有构建 GitHub 应用程序，您可能对[状态 API](/rest/reference/commits#commit-statuses) 感兴趣。
diff --git a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
index e1409a47ad..7111b2d945 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else  %}
 1. 在 Setting（设置）边栏中，单击 **Audit log（审核日志）**。 ![边栏中的组织审核日志设置](/assets/images/help/organizations/org-settings-audit-log.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
index 059906212d..1a327d39fa 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else  %}
 3. 在左侧边栏中，单击 **Audit log（审核日志）**。 ![审核日志选项卡](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/billing/license-statuses.md b/translations/zh-CN/data/reusables/billing/license-statuses.md
new file mode 100644
index 0000000000..eea8e721f5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/billing/license-statuses.md
@@ -0,0 +1,6 @@
+{% ifversion ghec %}
+If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
+- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
+- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
+- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/translations/zh-CN/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
index 7db5b9879a..6664cbfafc 100644
--- a/translations/zh-CN/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
+++ b/translations/zh-CN/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+{% if code-scanning-task-lists %}
 
 {% note %}
 
diff --git a/translations/zh-CN/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/zh-CN/data/reusables/code-scanning/beta-codeql-ml-queries.md
new file mode 100644
index 0000000000..133b760b30
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -0,0 +1,9 @@
+{% if codeql-ml-queries %}
+
+{% note %}
+
+**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites-explanation.md
new file mode 100644
index 0000000000..af6fd15a54
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -0,0 +1,5 @@
+以下查询套件内置于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，可供使用。
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% if codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites.md b/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites.md
index f9b919f834..53e5dbe60f 100644
--- a/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites.md
+++ b/translations/zh-CN/data/reusables/code-scanning/codeql-query-suites.md
@@ -1,8 +1,4 @@
-以下查询套件内置于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，可供使用。
-
   | 查询套件                   | 描述                                      |
   |:---------------------- |:--------------------------------------- |
   | `security-extended`    | 严重性和精度低于默认查询的查询                         |
   | `security-and-quality` | 来自 `security-extended` 的查询，加上可维护性和可靠性查询 |
-
-在指定查询套件时，{% data variables.product.prodname_codeql %} 分析引擎将运行套件中包含的查询，以及默认查询集。
diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-billing.md b/translations/zh-CN/data/reusables/codespaces/codespaces-billing.md
index 3b9dc197a0..4c5e38bbf7 100644
--- a/translations/zh-CN/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/zh-CN/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
 {% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage.
 
 ### Calculating compute usage
-The total number of uptime minutes for which the {% data variables.product.prodname_codespaces %} instances are active. Compute usage is calculated by the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
+Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
 
-Uptime is controlled by stopping your codespace which can be done manually or based on period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
 
 ### Calculating storage usage
 For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 到月底，{% data variables.product.prodname_dotcom %} 会将您的存储量舍入到最接近的 MB。 
diff --git a/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md b/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
index 090e35d2e2..52c7d535ab 100644
--- a/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
+++ b/translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md
@@ -1,2 +1,5 @@
-1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**.{% ifversion fpt or ghec %} ![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/help/dependabot/dependabot-secrets.png){% else %}
-![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png){% endif %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
+{% elsif ghes > 3.2%}
+1. 在侧边栏中，单击 **{% data variables.product.prodname_dependabot %}**。 ![{% data variables.product.prodname_dependabot %} 密钥边栏选项](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md
index 5d4180b8ef..21c3437455 100644
--- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md
@@ -1 +1 @@
-If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)."
+If you need to reset the password for your setup user, contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/save-settings.md b/translations/zh-CN/data/reusables/enterprise_management_console/save-settings.md
index ad4495169a..abf2d6c5d8 100644
--- a/translations/zh-CN/data/reusables/enterprise_management_console/save-settings.md
+++ b/translations/zh-CN/data/reusables/enterprise_management_console/save-settings.md
@@ -1,2 +1,2 @@
 1. 在左侧边栏下，单击 **Save settings（保存设置）**。 ![{% data variables.enterprise.management_console %} 中的 Save settings 按钮](/assets/images/enterprise/management-console/save-settings.png)
-1. 等待配置运行完毕。
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..a1cc2ae3c0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.product.product_location %}.
+
+{% endwarning %}
diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..bfbfefb4de
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,3 @@
+1. 等待配置运行完毕。
+
+   ![配置实例](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/translations/zh-CN/data/reusables/gated-features/user-repo-collaborators.md b/translations/zh-CN/data/reusables/gated-features/user-repo-collaborators.md
index f560e75486..319b8698fd 100644
--- a/translations/zh-CN/data/reusables/gated-features/user-repo-collaborators.md
+++ b/translations/zh-CN/data/reusables/gated-features/user-repo-collaborators.md
@@ -1 +1,4 @@
-如果您使用的是 {% data variables.product.prodname_free_user %}，您可以在公共和私有仓库中添加无限的协作者。
+{% ifversion fpt %}
+If you're using
+{% data variables.product.prodname_free_user %}, you can add unlimited collaborators on public and private repositories.
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-activity-types.md b/translations/zh-CN/data/reusables/github-actions/actions-activity-types.md
new file mode 100644
index 0000000000..cf0e471d18
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/actions-activity-types.md
@@ -0,0 +1,22 @@
+Some events have activity types that give you more control over when your workflow should run. Use `on.<event_name>.types` to define the type of event activity that will trigger a workflow run.
+
+For example, the `issue_comment` event has the `created`, `edited`, and `deleted` activity types. If your workflow triggers on the `label` event, it will run whenever a label is created, edited, or deleted. If you specify the `created` activity type for the `label` event, your workflow will run when a label is created but not when a label is edited or deleted.
+
+```yaml
+on:
+  label:
+    types:
+      - created
+```
+
+If you specify multiple activity types, only one of those event activity types needs to occur to trigger your workflow. If multiple triggering event activity types for your workflow occur at the same time, multiple workflow runs will be triggered. For example, the following workflow triggers when an issue is opened or labeled. If an issue with two labels is opened, three workflow runs will start: one for the issue opened event and two for the two issue labeled events.
+
+```yaml
+on:
+  issue:
+    types:
+      - opened
+      - labeled
+```
+
+有关每个事件及其活动类型的更多信息，请参阅“[触发工作流程的事件](/actions/using-workflows/events-that-trigger-workflows)”。
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-filters.md b/translations/zh-CN/data/reusables/github-actions/actions-filters.md
new file mode 100644
index 0000000000..549ef0190e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/actions-filters.md
@@ -0,0 +1,11 @@
+Some events have filters that give you more control over when your workflow should run.
+
+For example, the `push` event has a `branches` filter that causes your workflow to run only when a push to a branch that matches the `branches` filter occurs, instead of when any push occurs.
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+      - 'releases/**'
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-multiple-types.md b/translations/zh-CN/data/reusables/github-actions/actions-multiple-types.md
new file mode 100644
index 0000000000..0a904faa5c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/actions-multiple-types.md
@@ -0,0 +1,18 @@
+If you specify activity types or filters for an event and your workflow triggers on multiple events, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration.
+
+For example, a workflow with the following `on` value will run when:
+
+- A label is created
+- A push is made to the `main` branch in the repository
+- A push is made to a {% data variables.product.prodname_pages %}-enabled branch
+
+```yaml
+on:
+  label:
+    types:
+      - created
+  push:
+    branches:
+      - main
+  page_build:
+```
diff --git a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md
index 9590cce8e5..26d4a25747 100644
--- a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md
+++ b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md
@@ -1,75 +1,19 @@
 ### Using a single event
 
-For example, a workflow with the following `on` value will run when a push is made to any branch in the workflow's repository:
-
-```yaml
-on: push
-```
+{% data reusables.github-actions.on-single-example %}
 
 ### Using multiple events
 
-You can specify a single event or multiple events. For example, a workflow with the following `on` value will run when a push is made to any branch in the repository or when someone forks the repository:
-
-```yaml
-on: [push, fork]
-```
-
-If you specify multiple events, only one of those events needs to occur to trigger your workflow. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered.
+{% data reusables.github-actions.on-multiple-example %}
 
 ### Using activity types
 
-Some events have activity types that give you more control over when your workflow should run.
-
-For example, the `issue_comment` event has the `created`, `edited`, and `deleted` activity types. If your workflow triggers on the `label` event, it will run whenever a label is created, edited, or deleted. If you specify the `created` activity type for the `label` event, your workflow will run when a label is created but not when a label is edited or deleted.
-
-```yaml
-on:
-  label:
-    types:
-      - created
-```
-
-If you specify multiple activity types, only one of those event activity types needs to occur to trigger your workflow. If multiple triggering event activity types for your workflow occur at the same time, multiple workflow runs will be triggered. For example, the following workflow triggers when an issue is opened or labeled. If an issue with two labels is opened, three workflow runs will start: one for the issue opened event and two for the two issue labeled events.
-
-```yaml
-on:
-  issue:
-    types:
-      - opened
-      - labeled
-```
+{% data reusables.github-actions.actions-activity-types %}
 
 ### Using filters
 
-Some events have filters that give you more control over when your workflow should run.
-
-For example, the `push` event has a `branches` filter that causes your workflow to run only when a push to a branch that matches the `branches` filter occurs, instead of when any push occurs.
-
-```yaml
-on:
-  push:
-    branches:
-      - main
-      - 'releases/**'
-```
+{% data reusables.github-actions.actions-filters %}
 
 ### Using activity types and filters with multiple events
 
-If you specify activity types or filters for an event and your workflow triggers on multiple events, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration.
-
-For example, a workflow with the following `on` value will run when:
-
-- A label is created
-- A push is made to the `main` branch in the repository
-- A push is made to a {% data variables.product.prodname_pages %}-enabled branch
-
-```yaml
-on:
-  label:
-    types:
-      - created
-  push:
-    branches:
-      - main
-  page_build:
-```
\ No newline at end of file
+{% data reusables.github-actions.actions-multiple-types %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/on-multiple-example.md b/translations/zh-CN/data/reusables/github-actions/on-multiple-example.md
new file mode 100644
index 0000000000..66a7708123
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/on-multiple-example.md
@@ -0,0 +1,7 @@
+You can specify a single event or multiple events. For example, a workflow with the following `on` value will run when a push is made to any branch in the repository or when someone forks the repository:
+
+```yaml
+on: [push, fork]
+```
+
+If you specify multiple events, only one of those events needs to occur to trigger your workflow. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered.
diff --git a/translations/zh-CN/data/reusables/github-actions/on-single-example.md b/translations/zh-CN/data/reusables/github-actions/on-single-example.md
new file mode 100644
index 0000000000..b8c7046c3e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/on-single-example.md
@@ -0,0 +1,5 @@
+For example, a workflow with the following `on` value will run when a push is made to any branch in the workflow's repository:
+
+```yaml
+on: push
+```
diff --git a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-options.md b/translations/zh-CN/data/reusables/github-actions/private-repository-forks-options.md
new file mode 100644
index 0000000000..4face09e25
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/private-repository-forks-options.md
@@ -0,0 +1,3 @@
+- **Run workflows from fork pull requests（从复刻拉取请求运行工作流程）** - 允许用户使用具有只读权限、没有密码访问权限的 `GITHUB_TOKEN`从复刻拉取请求运行工作流程。
+- **Send write tokens to workflows from pull requests（从拉取请求向工作流程发送写入令牌）** - 允许从复刻拉取请求以使用具有写入权限的 `GITHUB_TOKEN`。
+- **Send secrets to workflows from pull requests（从拉取请求向工作流程发送密码）** - 使所有密码可用于拉取请求。
diff --git a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md b/translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md
index cbf507d7ae..761c7e2db7 100644
--- a/translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md
+++ b/translations/zh-CN/data/reusables/github-actions/private-repository-forks-overview.md
@@ -1,5 +1 @@
-如果您依赖于使用私有仓库的复刻，您可以配置策略来控制用户如何在 `pull_request` 事件上运行工作流程。 Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.{% ifversion ghec or ghes or ghae %} For enterprises, the policies are applied to all repositories in all organizations.{% endif %}
-
-- **Run workflows from fork pull requests（从复刻拉取请求运行工作流程）** - 允许用户使用具有只读权限、没有密码访问权限的 `GITHUB_TOKEN`从复刻拉取请求运行工作流程。
-- **Send write tokens to workflows from pull requests（从拉取请求向工作流程发送写入令牌）** - 允许从复刻拉取请求以使用具有写入权限的 `GITHUB_TOKEN`。
-- **Send secrets to workflows from pull requests（从拉取请求向工作流程发送密码）** - 使所有密码可用于拉取请求。
+如果您依赖于使用私有仓库的复刻，您可以配置策略来控制用户如何在 `pull_request` 事件上运行工作流程。 Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories.
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
new file mode 100644
index 0000000000..c51ca1a34a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-check-mac-linux.md
@@ -0,0 +1,3 @@
+```shell
+./run.sh --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md
index b86d3f1e49..482e224aa3 100644
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md
+++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure.md
@@ -14,3 +14,6 @@
    - 运行 `config` 脚本配置自托管运行器应用程序，并向 {% data variables.product.prodname_actions %} 注册。 `config` 脚本需要目标 URL 和自动生成的时间限制令牌来验证请求。
      - 在 Windows上，`config` 脚本还会询问您是否想将自托管运行器应用程序安装为服务。 对于 Linux 和 macOS，您可以在完成添加运行器后安装服务。 更多信息请参阅“[将自托管运行器应用程序配置为服务](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)”。
    - 运行自托管运行器应用程序以将机器连接到 {% data variables.product.prodname_actions %}。
+{% ifversion fpt or ghec or ghes > 3.2 %}
+     - If you are setting up a cluster of runners, you can install another tool to automatically scale your runners.  更多信息请参阅“[使用自托管运行器自动缩放](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)”。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md b/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
index 011cc0a84b..4eabba8e7e 100644
--- a/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
+++ b/translations/zh-CN/data/reusables/github-actions/sidebar-secret.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧边栏中，单击 **Secrets（密码）**。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
index 383da9c0c7..a23bc3e851 100644
--- a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
@@ -64,10 +64,10 @@ Ubuntu 18.04
 macOS Big Sur 11
 </td>
 <td>
-<code>macos-11</code>
+<code>macos-latest</code> 或 <code>macos-11</code>
 </td>
 <td>
-The <code>macos-latest</code> label currently uses the macOS 10.15 runner image.
+The <code>macos-latest</code> label currently uses the macOS 11 runner image.
 </td>
 </tr>
 <tr>
@@ -75,7 +75,7 @@ The <code>macos-latest</code> label currently uses the macOS 10.15 runner image.
 macOS Catalina 10.15
 </td>
 <td>
-<code>macos-latest</code> 或 <code>macos-10.15</code>
+<code>macos-10.15</code>
 </td>
 <td>
 </td>
@@ -83,6 +83,12 @@ macOS Catalina 10.15
 </tbody>
 </table>
 
+{% note %}
+
+**Note:** The `-latest` virtual environments are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor.
+
+{% endnote %}
+
 {% warning %}
 
 <b>Note:</b> Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support.
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-dispatch-inputs.md b/translations/zh-CN/data/reusables/github-actions/workflow-dispatch-inputs.md
new file mode 100644
index 0000000000..641db1aa32
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/workflow-dispatch-inputs.md
@@ -0,0 +1,34 @@
+When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
+
+触发的工作流程接收 `github.event.input` 上下文中的输入。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。
+
+```yaml
+on:
+  workflow_dispatch:
+    inputs:
+      logLevel:
+        description: 'Log level'
+        required: true
+        default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
+        type: choice
+        options:
+        - info
+        - warning
+        - debug {% endif %}
+      tags:
+        description: 'Test scenario tags'
+        required: false {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5511 %}
+        type: boolean
+      environment:
+        description: 'Environment to run tests against'
+        type: environment
+        required: true {% endif %}
+
+jobs:
+  print-tag:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Print the input tag to STDOUT
+        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
+```
diff --git a/translations/zh-CN/data/reusables/organizations/billing-settings.md b/translations/zh-CN/data/reusables/organizations/billing-settings.md
index e7b3ec8d5a..feb35fd556 100644
--- a/translations/zh-CN/data/reusables/organizations/billing-settings.md
+++ b/translations/zh-CN/data/reusables/organizations/billing-settings.md
@@ -1,4 +1,4 @@
 {% data reusables.user_settings.access_settings %}
-2. 在设置侧边栏中，单击 **Organizations（组织）**。 ![侧边栏中的组织设置](/assets/images/help/settings/settings-sidebar-organizations.png)
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
 {% data reusables.profile.org_settings %}
-4. 如果您是组织所有者，请在左侧边栏中单击 **Billing & plans（帐单和计划）**。 ![组织设置侧边栏中的计划方案](/assets/images/help/organizations/billing-settings.png)
+1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/zh-CN/data/reusables/organizations/billing_plans.md b/translations/zh-CN/data/reusables/organizations/billing_plans.md
index 32b13ca571..ed5792ba3e 100644
--- a/translations/zh-CN/data/reusables/organizations/billing_plans.md
+++ b/translations/zh-CN/data/reusables/organizations/billing_plans.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在组织的 Settings（设置）侧边栏中，单击 **Billing & plans（帐单和计划）**。 ![帐单设置](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/block_users.md b/translations/zh-CN/data/reusables/organizations/block_users.md
index 93cece43b6..10efc741f5 100644
--- a/translations/zh-CN/data/reusables/organizations/block_users.md
+++ b/translations/zh-CN/data/reusables/organizations/block_users.md
@@ -1 +1 @@
-1. 在组织的 Settings（设置）侧边栏中，单击 **Blocked users（被阻止的用户）**。 ![组织设置中被阻止的用户](/assets/images/help/organizations/org-settings-block-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
diff --git a/translations/zh-CN/data/reusables/organizations/click-codespaces.md b/translations/zh-CN/data/reusables/organizations/click-codespaces.md
index fa9c09b609..2f409b474f 100644
--- a/translations/zh-CN/data/reusables/organizations/click-codespaces.md
+++ b/translations/zh-CN/data/reusables/organizations/click-codespaces.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Codespaces**。 ![左侧边栏中的"Codespaces"选项卡](/assets/images/help/organizations/codespaces-sidebar-tab.png)
+1. In the left sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
index b52ff17a49..a606fbb1fe 100644
--- a/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
+++ b/translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧边栏中，单击 **{% data variables.product.prodname_github_apps %}**。 ![{% data variables.product.prodname_github_apps %} 设置](/assets/images/help/organizations/github-apps-settings-sidebar.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/member-privileges.md b/translations/zh-CN/data/reusables/organizations/member-privileges.md
index af24c6cc18..e2427fc02c 100644
--- a/translations/zh-CN/data/reusables/organizations/member-privileges.md
+++ b/translations/zh-CN/data/reusables/organizations/member-privileges.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
+{% elsif ghae or ghes < 3.4 %}
 4. 在左侧边栏中，单击 **Member privileges（成员权限）**。 ![组织设置中的成员权限选项](/assets/images/help/organizations/org-settings-member-privileges.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/moderation-settings.md b/translations/zh-CN/data/reusables/organizations/moderation-settings.md
index 1760193680..b79fd4132d 100644
--- a/translations/zh-CN/data/reusables/organizations/moderation-settings.md
+++ b/translations/zh-CN/data/reusables/organizations/moderation-settings.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![Moderation settings in organization's settings](/assets/images/help/organizations/org-settings-moderation-settings.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**
diff --git a/translations/zh-CN/data/reusables/organizations/oauth_app_access.md b/translations/zh-CN/data/reusables/organizations/oauth_app_access.md
index 6b01d0f357..a2dc8773f5 100644
--- a/translations/zh-CN/data/reusables/organizations/oauth_app_access.md
+++ b/translations/zh-CN/data/reusables/organizations/oauth_app_access.md
@@ -1,3 +1 @@
-{% ifversion fpt or ghec %}
-  1. 在 Setting（设置）侧边栏中，单击 **Third-party access（第三方访问）**。 ![左侧边栏中的 {% data variables.product.prodname_oauth_app %} 访问选项卡](/assets/images/help/settings/settings-sidebar-third-party-access.png)
-{% endif %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
diff --git a/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md b/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md
index 36412844f2..937618670b 100644
--- a/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md
+++ b/translations/zh-CN/data/reusables/organizations/org-settings-repository-roles.md
@@ -1 +1 @@
-4. 在左边栏中，单击 **Repository roles（仓库角色）**。 ![组织设置中的仓库角色选项卡](/assets/images/help/organizations/org-settings-repository-roles.png)
+1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-label="The ID badge icon" %} Repository roles**.
diff --git a/translations/zh-CN/data/reusables/organizations/repository-defaults.md b/translations/zh-CN/data/reusables/organizations/repository-defaults.md
index 1482a43ed2..9d30bab3cc 100644
--- a/translations/zh-CN/data/reusables/organizations/repository-defaults.md
+++ b/translations/zh-CN/data/reusables/organizations/repository-defaults.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左边栏中，单击 **Repository defaults（仓库默认值）**。 ![仓库默认值选项卡](/assets/images/help/organizations/repo-defaults-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/repository-labels.md b/translations/zh-CN/data/reusables/organizations/repository-labels.md
index 0d9782e24b..29ff1db260 100644
--- a/translations/zh-CN/data/reusables/organizations/repository-labels.md
+++ b/translations/zh-CN/data/reusables/organizations/repository-labels.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Repository labels（仓库标签）**。 ![仓库标签选项卡](/assets/images/help/organizations/repo-labels-tab.png)
+1. 在左侧边栏中，单击 **Repository labels（仓库标签）**。
diff --git a/translations/zh-CN/data/reusables/organizations/security-and-analysis.md b/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
index 67cf5ff384..37774fc461 100644
--- a/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
+++ b/translations/zh-CN/data/reusables/organizations/security-and-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![组织设置中的"Security & analysis（安全和分析）"选项卡](/assets/images/help/organizations/org-settings-security-and-analysis.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/security.md b/translations/zh-CN/data/reusables/organizations/security.md
index ef78aea678..9a20cf5fe7 100644
--- a/translations/zh-CN/data/reusables/organizations/security.md
+++ b/translations/zh-CN/data/reusables/organizations/security.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
+{% else  %}
 1. 在左边栏中，单击 **Organization security（组织安全）**。
 
  ![组织安全设置](/assets/images/help/organizations/org-security-settings-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/teams_sidebar.md b/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
index c9a4975123..8725b2c756 100644
--- a/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
+++ b/translations/zh-CN/data/reusables/organizations/teams_sidebar.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
 1. 在 Settings（设置）侧边栏中，单击 **Teams（团队）**。 ![组织设置侧边栏中的团队选项卡](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/verified-domains.md b/translations/zh-CN/data/reusables/organizations/verified-domains.md
index 4f14c36bf6..2c428cfd09 100644
--- a/translations/zh-CN/data/reusables/organizations/verified-domains.md
+++ b/translations/zh-CN/data/reusables/organizations/verified-domains.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧边栏中，单击 **Verified & approved domains（已验证并批准的域名）**。 ![“已验证并批准的域名”选项卡](/assets/images/help/organizations/verified-domains-button.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/pages/sidebar-pages.md b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
index 542e8e1d28..39aac8496d 100644
--- a/translations/zh-CN/data/reusables/pages/sidebar-pages.md
+++ b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
@@ -1,3 +1,5 @@
-{% ifversion fpt or ghes > 3.1 or ghec %}
+{% ifversion fpt or ghes > 3.3 or ghec or ghae-issue-5658 %}
+1. In the "Code & operations" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
+{% else %}
 1. 在左侧边栏中，单击 **Pages（页面）**。 ![左侧边栏中的页面选项卡](/assets/images/help/pages/pages-tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/profile/org_member_privileges.md b/translations/zh-CN/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..c0462ae849
--- /dev/null
+++ b/translations/zh-CN/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1 @@
+3. Under "Access", click **Member privileges**. ![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png) 
diff --git a/translations/zh-CN/data/reusables/reminders/scheduled-reminders.md b/translations/zh-CN/data/reusables/reminders/scheduled-reminders.md
index c71cf07ead..b45b072c3c 100644
--- a/translations/zh-CN/data/reusables/reminders/scheduled-reminders.md
+++ b/translations/zh-CN/data/reusables/reminders/scheduled-reminders.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Scheduled reminders（预定提醒）**。
+1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-label="The clock icon" %} Scheduled reminders**.
diff --git a/translations/zh-CN/data/reusables/repositories/click-collaborators-teams.md b/translations/zh-CN/data/reusables/repositories/click-collaborators-teams.md
new file mode 100644
index 0000000000..300fea61ad
--- /dev/null
+++ b/translations/zh-CN/data/reusables/repositories/click-collaborators-teams.md
@@ -0,0 +1 @@
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Collaborators & teams**.
diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
index 957be37239..5db73f5e10 100644
--- a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![仓库设置中的"Security & analysis（安全和分析）"选项卡](/assets/images/help/repository/security-and-analysis-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/repository-branches.md b/translations/zh-CN/data/reusables/repositories/repository-branches.md
index 73e04bea88..679e2d97d8 100644
--- a/translations/zh-CN/data/reusables/repositories/repository-branches.md
+++ b/translations/zh-CN/data/reusables/repositories/repository-branches.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code & operations" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
+{% elsif ghes < 3.4 or ghae %}
 1. 在左侧菜单中，单击 **Branches（分支）**。 ![仓库选项子菜单](/assets/images/help/repository/repository-options-branch.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-moderation-reported-content.md b/translations/zh-CN/data/reusables/repositories/sidebar-moderation-reported-content.md
index 09e191d5ec..6d184ae816 100644
--- a/translations/zh-CN/data/reusables/repositories/sidebar-moderation-reported-content.md
+++ b/translations/zh-CN/data/reusables/repositories/sidebar-moderation-reported-content.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Reported content（已报告的内容）**。 ![仓库 Settings（设置）侧边栏中的“Reported content（已报告的内容）”](/assets/images/help/repository/repo-settings-reported-content.png)
+1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Reported content**.
diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md b/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
index 28fc5bc9a4..a5de73765d 100644
--- a/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
+++ b/translations/zh-CN/data/reusables/repositories/sidebar-notifications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
 1. 单击 **Notifications（通知）**。 ![侧边栏中的通知按钮](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 9bb6d6cc97..a92cceeae9 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -155,6 +155,8 @@ Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key
 PyPI | PyPI API Token | pypi_api_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae %}
+Segment | Segment Public API Token | segment_public_api_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
diff --git a/translations/zh-CN/data/reusables/security/compliance-report-list.md b/translations/zh-CN/data/reusables/security/compliance-report-list.md
new file mode 100644
index 0000000000..7bce73219d
--- /dev/null
+++ b/translations/zh-CN/data/reusables/security/compliance-report-list.md
@@ -0,0 +1,4 @@
+- SOC 1, Type 2
+- SOC 2, Type 2
+- Cloud Security Alliance CAIQ self-assessment (CSA CAIQ)
+- {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/security/compliance-report-screenshot.md b/translations/zh-CN/data/reusables/security/compliance-report-screenshot.md
new file mode 100644
index 0000000000..984c8d6d8b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/security/compliance-report-screenshot.md
@@ -0,0 +1 @@
+![Screenshot of download button to the right of a compliance report](/assets/images/help/settings/compliance-report-download.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/sponsors/sponsors-only-repos.md b/translations/zh-CN/data/reusables/sponsors/sponsors-only-repos.md
new file mode 100644
index 0000000000..0361572c97
--- /dev/null
+++ b/translations/zh-CN/data/reusables/sponsors/sponsors-only-repos.md
@@ -0,0 +1 @@
+You can give all sponsors in a tier access to a private repository by adding the repository to the tier.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/sponsors/tier-details.md b/translations/zh-CN/data/reusables/sponsors/tier-details.md
index 5a698121ed..ed6a1a0f92 100644
--- a/translations/zh-CN/data/reusables/sponsors/tier-details.md
+++ b/translations/zh-CN/data/reusables/sponsors/tier-details.md
@@ -3,10 +3,11 @@
 您可以自定义每个等级的奖励。 例如，一个等级的奖励可以包括：
 - 提早使用新版本
 - README 中的徽标或名称
-- 访问私有仓库
 - 每周时事通讯更新
 - 您的赞助者将享受其他奖励 ✨
 
+{% data reusables.sponsors.sponsors-only-repos %} For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)."
+
 您可以加入欢迎消息，其中包含有关访问或接收奖励的信息，这些信息在付款后和欢迎电子邮件中可见。
 
 一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 现有赞助者将保留在已撤销的等级中，直到他们更改其赞助等级、取消其赞助或其一次性赞助期满。
diff --git a/translations/zh-CN/data/reusables/user-settings/oauth_apps.md b/translations/zh-CN/data/reusables/user-settings/oauth_apps.md
index c942d79126..05f0a79025 100644
--- a/translations/zh-CN/data/reusables/user-settings/oauth_apps.md
+++ b/translations/zh-CN/data/reusables/user-settings/oauth_apps.md
@@ -1 +1 @@
-1. 在左边栏中，单击 **OAuth Apps（OAuth 应用程序）**。 ![OAuth 应用程序部分](/assets/images/help/settings/developer-settings-oauth-apps.png)
+1. 在左侧边栏中，单击 **{% data variables.product.prodname_oauth_apps %}**。 ![OAuth 应用程序部分](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/access_applications.md b/translations/zh-CN/data/reusables/user_settings/access_applications.md
index 22e6ffde79..1c307bc2a7 100644
--- a/translations/zh-CN/data/reusables/user_settings/access_applications.md
+++ b/translations/zh-CN/data/reusables/user_settings/access_applications.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
 1. 在左侧边栏中，单击 **Applications**。 ![应用程序选项卡](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/accessibility_settings.md b/translations/zh-CN/data/reusables/user_settings/accessibility_settings.md
index b23486a3ff..2c9e37e2f4 100644
--- a/translations/zh-CN/data/reusables/user_settings/accessibility_settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/accessibility_settings.md
@@ -1 +1 @@
-1. In the navigation on the left hand side, click the **Accessibility** link. ![Screenshot of the user settings navigation. The Accessibility link is highlighted.](/assets/images/help/settings/accessibility-tab.png)
+1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**.
diff --git a/translations/zh-CN/data/reusables/user_settings/account_settings.md b/translations/zh-CN/data/reusables/user_settings/account_settings.md
index 3638f2871a..e3cd5d53e4 100644
--- a/translations/zh-CN/data/reusables/user_settings/account_settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/account_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-next %}
+1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
+{% else %}
 1. 在左侧边栏中，单击 **Account（帐户）**。 ![帐户设置菜单选项](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/appearance-settings.md b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
index 81424365c6..fdd66ad0d7 100644
--- a/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
@@ -1,3 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
 1. 在用户设置侧边栏中，单击 **Appearance（外观）**。
 
-   ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
+   ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/user_settings/billing_plans.md b/translations/zh-CN/data/reusables/user_settings/billing_plans.md
index 704e61bc4d..333102205b 100644
--- a/translations/zh-CN/data/reusables/user_settings/billing_plans.md
+++ b/translations/zh-CN/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. 在用户设置侧边栏中，单击 **Billing & plans（帐单与计划）**。 ![帐单与计划设置](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
diff --git a/translations/zh-CN/data/reusables/user_settings/blocked_users.md b/translations/zh-CN/data/reusables/user_settings/blocked_users.md
index 9ea134fc86..b7ba502dca 100644
--- a/translations/zh-CN/data/reusables/user_settings/blocked_users.md
+++ b/translations/zh-CN/data/reusables/user_settings/blocked_users.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Blocked users** under **Moderation settings**. ![被阻止的用户选项卡](/assets/images/help/settings/settings-sidebar-blocked-users.png)
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**.
diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md b/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md
index a55f54e643..5aa532885e 100644
--- a/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md
+++ b/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Codespaces**。 ![用户设置侧边栏中的 Codespaces 选项卡](/assets/images/help/settings/codespaces-tab.png)
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/zh-CN/data/reusables/user_settings/developer_settings.md b/translations/zh-CN/data/reusables/user_settings/developer_settings.md
index fcf644f8b9..bd27b9e487 100644
--- a/translations/zh-CN/data/reusables/user_settings/developer_settings.md
+++ b/translations/zh-CN/data/reusables/user_settings/developer_settings.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %}
 1. 在左侧边栏中，单击 **Developer settings**。 ![开发者设置](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/emails.md b/translations/zh-CN/data/reusables/user_settings/emails.md
index 22083af940..872d53bdea 100644
--- a/translations/zh-CN/data/reusables/user_settings/emails.md
+++ b/translations/zh-CN/data/reusables/user_settings/emails.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
 1. 在左侧边栏中，单击 **Emails（电子邮件）**。 ![电子邮件选项卡](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/organizations.md b/translations/zh-CN/data/reusables/user_settings/organizations.md
index 3df184cdfe..d593508a58 100644
--- a/translations/zh-CN/data/reusables/user_settings/organizations.md
+++ b/translations/zh-CN/data/reusables/user_settings/organizations.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
 1. 在用户设置侧边栏中，单击 **Organizations（组织）**。 ![组织的用户设置](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/repo-tab.md b/translations/zh-CN/data/reusables/user_settings/repo-tab.md
index e5d4521b02..84701bb7be 100644
--- a/translations/zh-CN/data/reusables/user_settings/repo-tab.md
+++ b/translations/zh-CN/data/reusables/user_settings/repo-tab.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
 1. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/saved_replies.md b/translations/zh-CN/data/reusables/user_settings/saved_replies.md
index e894761ec5..45ece51af1 100644
--- a/translations/zh-CN/data/reusables/user_settings/saved_replies.md
+++ b/translations/zh-CN/data/reusables/user_settings/saved_replies.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
 1. 在左侧边栏中，单击 **Saved replies（已保存回复）**。 ![已保存回复选项卡](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/security-analysis.md b/translations/zh-CN/data/reusables/user_settings/security-analysis.md
index 754ff74f87..6fb9cc957f 100644
--- a/translations/zh-CN/data/reusables/user_settings/security-analysis.md
+++ b/translations/zh-CN/data/reusables/user_settings/security-analysis.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![安全和分析设置](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/security.md b/translations/zh-CN/data/reusables/user_settings/security.md
index 41285e94c1..8998e91180 100644
--- a/translations/zh-CN/data/reusables/user_settings/security.md
+++ b/translations/zh-CN/data/reusables/user_settings/security.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
 1. 在左侧边栏中，单击 **Account security（帐户安全）**。 ![用户帐户安全设置](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/ssh.md b/translations/zh-CN/data/reusables/user_settings/ssh.md
index 56ec9e7e15..35ecc516f5 100644
--- a/translations/zh-CN/data/reusables/user_settings/ssh.md
+++ b/translations/zh-CN/data/reusables/user_settings/ssh.md
@@ -1 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5658 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
 1. 在用户设置侧边栏中，单击 **SSH and GPG keys（SSH 和 GPG 密钥）**。 ![身份验证密钥](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index c9552e1e20..190081755e 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -13,6 +13,7 @@ header:
     ghes_release_notes_upgrade_patch_only: '📣 这不是 Enterprise Server 最新的<a href="#{{ latestPatch }}">补丁版本</a>。'
     ghes_release_notes_upgrade_release_only: '📣 这不是 Enterprise Server 的<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新版本</a>。'
     ghes_release_notes_upgrade_patch_and_release: '📣 这不是此版本系列的<a href="#{{ latestPatch }}">最新修补版</a>，也不是 Enterprise Server 的<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新版本</a>。'
+  sign_up_cta: 注册
 picker:
   language_picker_default_text: Choose a language
   product_picker_default_text: All products
@@ -37,11 +38,12 @@ toc:
   guides: 指南
   whats_new: 新增内容
   videos: 视频
+  all_changelogs: All changelog posts
 pages:
   article_version: '文章版本'
   miniToc: 本文内容
   contributor_callout: 这篇文章的参与者和维护者是
-  all_enterprise_releases: 所有企业版本
+  all_enterprise_releases: All Enterprise Server releases
 errors:
   oops: 哎呀！
   something_went_wrong: 看来出现了错误。
@@ -159,10 +161,12 @@ product_landing:
   release_notes_for: 发行说明
   upgrade_from: 升级自
   browse_all_docs: 浏览所有文档
+  browse_all: Browse all
+  docs: 文档
   explore_release_notes: 浏览发行说明
+  view: 查看所有
 product_guides:
-  start: 开始
-  start_path: 开始路径
+  start_path: Start learning path
   learning_paths: '{{ productMap[currentProduct].name }} 学习路径'
   learning_paths_desc: 学习路径是一系列帮助您掌握特定主题的指南。
   guides: '{{ productMap[currentProduct].name }} 指南'